Neues vom PostgreSQL Planet
Dan Langille: Galène: fixing double-encoded port files
uzair aslam: PostgreSQL Connection Pooling on Vercel with Next.js
Configure PostgreSQL connection pooling on Vercel with Next.js. Size pg pools, release clients, handle transactions, and reproduce queued requests locally.
Your Next.js endpoint works locally, then starts timing out after a deployment or traffic spike. PostgreSQL reports too many connections, or requests wait even though the database has little CPU activity. Adding more function instances can make the problem worse because each instance can open another group of connections.
Vibhor Kumar: Relevance Is Not Permission: Filter-First Vector Search in PostgreSQL
Picture an internal assistant that answers employee questions from a shared document store. Someone asks a reasonable question about bonus timelines. The vector search does exactly what it was built to do and finds the most semantically similar chunks. One of those chunks comes from a compensation review meant only for HR.
Jimmy Angelakos: postgres.scot November 2026: a live Radar demo and Call for Presentations for December meetup
Yesterday, Thursday, November 19th, was a cold night in Edinburgh, but the wonderful Law School in the University of Edinburgh's Old College was warm and cosy for our November meetup.
Aleksei Aleinikov: PostgreSQL 19 vs 18: Native REPACK, pg_plan_advice, Graph Myth & Production Upgrade Guide
If PostgreSQL 18 was the storage-speed release that brought Asynchronous I/O (io_uring and worker threads) to Postgres, PostgreSQL 19 is the operational release DBAs and backend teams have been asking for since 2018.
Zsolt Parragi: What's left in Postgres 19
Yesterday, PostgreSQL 19 was finally released after multiple delays. Everyone already knows about the many reverts that happened, but what actually remains? Is it still an interesting release?
This blog post doesn’t aim to be a complete list: the release notes are there for that.
Ahsan Hadi: PostgreSQL 19 is Here: Worth the Wait
PostgreSQL 19 was released today. pgEdge packages for it are available the same day across all of our supported deployments - including Spock, where PG 19 support is already available. I have been testing the release candidates for a few weeks, so here is what I think matters most to DBAs and teams. replaces and , and with the option it rebuilds a bloated table without blocking reads and writes. In my own test, inserts kept running at about 2,000 a second with no failed transactions while a bloated table was rebuilt in under a second.
Dave Stokes: Using dbvr with PostgreSQL: From First Datasource to Production Queries
dbvr lets you define PostgreSQL connections and run SQL from the command line, with no graphical interface. That makes it a fit for servers, containers, and pipelines where a desktop database tool cannot run.
David Wheeler: pg_clickhouse 0.11.1: Now with pgvector, UPDATE, DELETE pushdown
Don't let the minor version increment fool you: pg_clickhouse v0.11.1, released last week, delivers a slew of improvements and bug fixes, including UPDATE, DELETE, TRUNCATE, and pgvector search pushdown.
pgvector type mappingLet's start with the latter: pgvector type mapping. Given this ClickHouse table:
CALL clickhouse_perform('ch_server', $$ CREATE TABLE items ( id Int32, category String, v Array(Float32) ) ENGINE = MergeTree ORDER BY (id); $$);
Radim Marek: Your biggest tenant runs someone else's plan
This one started with RegreSQL. Since The tests passed. The plan didn't. I've been loading production statistics into empty databases to see how much the plans alone can tell about a real workload. One paginated endpoint in a multi-tenant app wouldn't line up. Its plan was cheap, a cost of a few hundred and an estimate of one row, while pg_stat_statements in production had the same query reading thousands of buffers per call to return about eight rows.
Cornelia Biacsics: Contributions for week 45
The following speakers delivered sessions about PostgreSQL at PASS Data Community Summit, which happened from 9-11 November 2026:
Álvaro Herrera: Squeezing tables with Postgres 19
Working with the Postgres development community is such a rewarding experience.
In January 2024, Pavel Stehule asked in the hackers mailing list: why is there no VACUUM FULL CONCURRENTLY?
Andrew Dunstan: New Security Infrastructure for PostgreSQL
Since June 2026, PostgreSQL security fixes have had a home of their own: a private git repository holding every pending fix as a stack of patches, and a private buildfarm that builds and tests that stack across every supported branch, continuously, before anything goes public.
damien clochard: PGRX 0.20: Build your own RPM/DEB packages
Writing a Postgres extension in Rust with pgrx is a lot of fun. You write a few functions in Rust, launch an instance with cargo pgrx run and you can call these functions directly inside Postgres.
With cargo pgrx test and cargo pgrx regress, you can run unit tests and regression checks against any major version of Postgres until everything is green. Then comes the last step, and it’s the least fun one: shipping it.
Nikolay Samokhvalov: The hidden costs of CREATE TEMP TABLE: catalog bloat and LWLock:SInvalWrite
salaheddine el hssani: Checking a compiler against a second implementation
A test says what its author expected. When the author also wrote the code, both come from the same reading of the problem, and a mistake in that reading is in both. They agree, the test passes, and the bug ships. Below is one way out of that loop for code whose answers can be computed another way: write a second implementation that is slow and plain, and compare the two on inputs neither author chose. It covers what that comparison found in a policy compiler, what it missed, and why the second implementation needs checks of its own.
Kaarel Moppel: A public safety reminder - large Postgres instances love huge pages
Dimitri Fontaine: Distributed primary keys
On a single Postgres server, primary keys stay unique because only one sequence hands out the numbers: a bigint identity column asks it for the next one, and no two rows ever get the same. Now put writers in several regions, each of them accepting inserts while the links between them are slow or down. Two regions that each ask their own sequence for “the next number” will hand out the same one, and the first time those two rows meet on a subscriber, one of them is rejected.
Jan Wieremjewicz: PGConf.EU 2026: It's About More Than PostgreSQL
Autumn is the time when leaves change color and fall. It’s also the time when new PostgreSQL releases come out, or at least that’s been the tradition for quite a while.
There’s one more thing that autumn brings to the PostgreSQL world: PGConf.EU, the annual conference that has grown into the largest PostgreSQL community event.
This year we met in Valencia, Spain. And while I’ve attended several editions already, 2026 brought quite a few firsts for me.
Aleksei Aleinikov: PostgreSQL in Docker for Production: Volumes, Shared Memory, Pooling & Backups
Running PostgreSQL in Docker takes ten seconds to start in development — and about ten minutes to lose data in production if you copy a default compose.yaml snippet from a tutorial.
Most outages with containerized Postgres are not caused by Docker itself. They happen because Docker’s defaults (64 MB /dev/shm, a 10-second SIGKILL timeout, unpinned :latest tags, and outdated PGDATA volume paths) collide directly with how PostgreSQL manages memory, checkpoints, and disk files.
Seiten
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- …
- nächste Seite ›
- letzte Seite »
