Analysis updated 2026-08-03 · repo last pushed 2019-12-28
Quickly check if a session ID exists in a large user-events table without a full scan.
Pre-check whether a value exists before running more expensive database lookups.
Filter or deduplicate data in analytics pipelines by skipping known-absent values.
| petere/pgbloomagg | reescalder/agent-memory-supabase | omarish/llm-sql | |
|---|---|---|---|
| Stars | 7 | 2 | 1 |
| Language | PLpgSQL | PLpgSQL | PLpgSQL |
| Last pushed | 2019-12-28 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 2/5 | 3/5 | 4/5 |
| Audience | data | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
The README is empty so you must read the PL/pgSQL source files directly to figure out installation and usage.
The README doesn't go into detail, but the repository name and description tell the core story: pgBloom adds a "bloom filter aggregate function" to PostgreSQL databases. In practical terms, this is a tool that lets a database quickly figure out whether something is probably present in a large set of data, or definitely not present, without scanning every single row. That can make certain queries much faster, especially when you are working with large tables and just need a fast yes-or-no answer. A bloom filter is a compact data structure that trades certainty for speed and space. Instead of storing the actual data, it stores a small summary that can answer "is this item in the set?" with either "maybe" or "definitely not." When you use it as a database aggregate function, you can build this summary across many rows at once. This is useful for tasks like filtering, deduplication, or pre-checking whether a value exists before doing more expensive lookups. The tradeoff is that a bloom filter can occasionally produce a false positive (saying something is present when it actually isn't), but it will never miss something that is genuinely there. The people who would reach for this are database administrators, backend developers, or data engineers working with PostgreSQL at scale. For example, if you have a large user-events table and want to quickly check whether a particular session ID has ever appeared, a bloom filter can give you a fast answer without scanning millions of rows. It is also useful in analytics pipelines or caching layers where you want to skip unnecessary work. The project is written in PL/pgSQL, which is PostgreSQL's built-in procedural language. Since the README is otherwise empty, the best way to understand how to install and use it would be to look at the code files in the repository directly.
Adds a bloom filter aggregate function to PostgreSQL, letting you quickly check if an item probably exists in a large dataset without scanning every row.
Mainly PLpgSQL. The stack also includes PostgreSQL, PLpgSQL.
Dormant — no commits in 2+ years (last push 2019-12-28).
No license information is provided in the README, so default copyright restrictions may apply.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly data.
This repo across BitVibe Labs
Verify against the repo before relying on details.