postgres

60 stories and discussions about postgres, aggregated from every source we track.

1.

TIN is a fast, full-featured, full-text search index for Postgres

228 points•ksec•2 months ago•95 comments•
2.
154 points•birdculture•about 2 months ago•91 comments•
3.

Paste SQL, parse it locally, and catch Postgres migration lock and rewrite risks before deploy.

116 points•vira28•about 2 months ago•40 comments•
4.

Postgres SELECT DISTINCT performs surprisingly poorly. We explain why and how we mitigated it.

83 points•KraftyOne•about 2 months ago•23 comments•
5.

Release blog post for Citus 11, which is now fully open source and includes the non-blocking shard rebalancer. Citus 11 also includes automatic schema and metadata syncing across nodes, enabling you to query from any…

39 points•docteurklein•over 4 years ago•4 comments
7.

Why Postgres connection poolers still choke on client-side TCP bottlenecks, how QUIC stream multiplexing solves the 30ms latency wall, and real benchmark numbers.

13 points•tenesripranav•about 2 months ago•2 comments•
9.

One app, two identical Postgres 17 databases, same region. Local was 4 to 7 times faster on reads because of network latency paid per query. Managed capped at 25 connections with 11 already used, and failed outright past 20 clients until I added the pooler.

7 points•remdore•about 2 months ago•0 comments
10.

We wrote six ordinary Postgres migrations: a new column, a unique index, a reporting index, a wider...

7 points•devopsdaily•about 2 months ago•0 comments
11.

Start in the pgEdge cloud. Deploy in our cloud, your cloud, or on-premises, including air-gapped environments.

6 points•bonesmoses•about 2 months ago•0 comments•
13.

Profiling and optimizing the Kafgres Postgres extension to achieve 700 MB/s write throughput and 600k evt/s on a single machine.

4 points•theanonymousone•about 2 months ago•0 comments•
14.

A free embed that turns the SQL in your blog posts into real Postgres queries readers can edit and run without leaving the page.

4 points•mikenikles•about 2 months ago•0 comments•
15.

In April I had to record a screen video for Meta’s app review (a huge pain, to be honest). The feature I was showing needed a permission Meta hadn’t granted yet, so I couldn’t turn it on for everyone. Recording it…

3 points•mazeez•about 2 months ago•0 comments•
16.

Scan a Postgres credential's effective privileges. Contribute to vaultkit-inc/agent-db-scan development by creating an account on GitHub.

3 points•nd_baba1•about 2 months ago•0 comments•
17.

How ClickHouse’s Postgres extensions handle the memory safety challenges of combining C and C++, from clean language boundaries to isolated helper processes.

3 points•__s•about 2 months ago•0 comments•
18.
3 points•barddoo•about 2 months ago•0 comments•
19.

Postgres change data capture for .NET: stream row changes through typed transforms into Meilisearch, Elasticsearch, OpenSearch, Kafka, pgvector or any HTTP endpoint.

3 points•Hawxy•about 2 months ago•0 comments•
20.

Embedding a performant singleton Kafka broker into Postgres.

3 points•topicpartition•about 2 months ago•1 comment
21.

Embedding a performant singleton Kafka broker into Postgres.

3 points•enether•about 2 months ago•0 comments•
22.

How a full-text search engine works, and how it works in Postgres

3 points•ksec•2 months ago•0 comments•
23.

Rails Validations vs Postgres Check Constraints

3 points•pushcx•about 11 years ago•0 comments
24.

What's New with Monitoring in PostgreSQL 19

2 points•saisrirampur•about 2 months ago•0 comments•
25.

How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.

2 points•saisrirampur•about 2 months ago•0 comments•
26.
2 points•Tomte•about 2 months ago•0 comments•
27.

Suggest the indexing strategy for your database . Contribute to abhiraj-ku/iCli development by creating an account on GitHub.

2 points•abhirajabhi312•about 2 months ago•0 comments•
28.

How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.

2 points•saisrirampur•about 2 months ago•0 comments•
29.

An extension for PostgreSQL that allows embedded Haskell code. - ed-o-saurus/PLHaskell

2 points•dewey•about 2 months ago•0 comments•
30.
2 points•piccirello•about 2 months ago•0 comments•
31.

How an inefficient Row-Level Security policy drove Postgres CPU to 80%; and why EXPLAIN failed to reveal it.

2 points•bucket2015•about 2 months ago•1 comment•
32.

Paste your CREATE TABLE statements and generate referentially intact Postgres data. No database, no connection string, no config. Weavori's DDL paste mode runs from a schema file.

2 points•ammarmalik17•about 2 months ago•0 comments•
33.

Relationship based access control for Postgres. Contribute to paulharter/letter development by creating an account on GitHub.

2 points•paulharter•about 2 months ago•3 comments•
34.

What's New with Monitoring in PostgreSQL 19

2 points•saisrirampur•2 months ago•0 comments•
35.

Your app, its database and its sign-in on one dedicated machine, run for you: tested backups, TLS, API, MCP. From $15 a month, nothing metered.

2 points•evgenileonti•2 months ago•0 comments•
36.

Worry-free Postgres for SaaS. Built to scale out. So you can focus on your app—not your database.

2 points•craigkerstiens•over 10 years ago•0 comments
37.

How ClickHouse’s Postgres extensions handle the memory safety challenges of combining C and C++, from clean language boundaries to isolated helper processes.

1 points•saisrirampur•about 2 months ago•0 comments•
38.
1 points•moonikakiss•about 2 months ago•0 comments•
39.

Jev detects the PII and a SQL function enforces who can see it

1 points•thruflo22•about 2 months ago•0 comments•
40.

A detailed explanation of Postgres deletions and how to avoid poor deletion and garbage collection performance.

1 points•KraftyOne•about 2 months ago•0 comments•
41.

The claims that AI is finding bugs so severe we have to revert patches seems inaccurate.

1 points•adastral•about 2 months ago•0 comments•
42.
1 points•fanf•about 2 months ago•1 comment
43.

ADD CONSTRAINT UNIQUE runs in milliseconds and locks nothing that matters, then aborts on a duplicate email. Fixtures hide it and so does uniform random data. Here is the data shape that exposes it.

1 points•ammarmalik17•about 2 months ago•0 comments•
44.

Read-only Postgres MCP server: a drop-in replacement for the archived server-postgres, with schema context for correct answers. - contextflo/postgres-mcp

1 points•depthfirst•about 2 months ago•1 comment•
45.

How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.

1 points•saisrirampur•about 2 months ago•0 comments•
46.

Follow a SQL query through the router, across four Postgres shards, and back.

1 points•hollylawly•about 2 months ago•0 comments•
47.

Your CI database picks different plans than production because its statistics differ. Inject production stats with PostgreSQL 18, or generate rows that carry the distribution. Here is how to tell which one you need.

1 points•ammarmalik17•about 2 months ago•0 comments•
48.

How a full-text search engine works, and how it works in Postgres

1 points•eigenBasis•about 2 months ago•0 comments•
49.

A long time ago I ran a write-heavy system on a hub and a handful of workers. Each worker took a share of the application traffic and wrote events locally. The …

1 points•hnp9j9qtda•about 2 months ago•0 comments•
50.

WalShadow replicates PostgreSQL to ClickHouse by decoding the physical WAL stream itself, not logical decoding.

1 points•nightshade999•about 2 months ago•0 comments•
51.

It’s been a month since I published the first part of this research, and interest from the Postgres community has been higher than I expected. Most vendors I contacted were shy to respond, so the Databricks…

1 points•jesdo•2 months ago•0 comments•
52.

Execute chDB queries in Postgres. Contribute to ClickHouse/pg_chdb development by creating an account on GitHub.

1 points•saisrirampur•2 months ago•0 comments•
53.

Postgres 19 is delayed due to late-stage feature reversions and AI-driven bug detection. Learn what features were pulled and what to expect next.

1 points•craigkerstiens•2 months ago•0 comments•
54.

Exception-only error monitoring. Sentry SDK compatible. 2-container self-host. - epure-sh/epure

1 points•nonmaskable•2 months ago•0 comments•
55.

Have you seen this legendary SQL iceberg meme? Let's talk about it while wearing our PostgreSQL hat!

1 points•gregsadetsky•2 months ago•0 comments•
56.

The SQL parser powering pgdog.dev. Contribute to pgdogdev/pg_raw_parse development by creating an account on GitHub.

1 points•levkk•2 months ago•0 comments•
57.

A fencing token is not a paragraph. It is a counter that must rise on a clock, die on a deadline, and...

1 points•aiio_6471•2 months ago•0 comments
58.

<p>Hi,</p> <p>In our previous post titled "Do we really need a specialized vector database?" on HN (<a href="https://news.ycombinator.com/item?id=37097004" rel="ugc">https://news.ycombinator.com/item?id=37097004</a>) we discussed the importance of using a Postgres-based solution for vector search. However, we acknowledged that existing Postgres vector extensions lack support for metadata filtering.</p> <p>We are excited to announce that we have now addressed this limitation. We are proud to be the first (<a href="https://github.com/tensorchord/pgvecto.rs" rel="ugc">https://github.com/tensorchord/pgvecto.rs</a>) to enable conditional filtering directly on HNSW indexes within Postgres. This breakthrough allows for efficient and effective metadata filtering in combination with vector search, eliminating the tradeoff previously associated with using Postgres for this purpose.</p> <p>We invite you to explore our updated offering and experience the benefits of seamless metadata filtering within a Postgres-based vector search system.</p>

1 points•gaocegege•about 3 years ago•0 comments
59.

<p>The ORM we use didn't support transactions so I wrote this! Hope it's useful.</p>

1 points•kb•about 11 years ago•0 comments
60.

Testing semantic search, filtered queries, and multi-table joins in AlloyDB to measure the true cost...

0 points•gleb_otochkin•about 2 months ago•0 comments

Related topics