Postgres 18: a CTE ran 23x the TPS of a temp table per transaction. With 5000 idle sessions, temp-table DDL got 127 and 249 of a 500 TPS target in...
Because your data is your business.
PGX is a specialist PostgreSQL consultancy. Founded in 2009, we are deep PostgreSQL experts, with decades of experience in everything from data-corruption repair and emergency response through tuning and troubleshooting to strategic data planning.
Support and consulting, tailored to your needs.
A suite of named offerings, from fast emergency help to ongoing managed uptime and focused project work — tailored to organizations of any size.
PGXpress™
Rapid emergency response for production incidents — corruption, outages, and the can't-wait moments.
CloudDBA™
Fully managed Postgres uptime — monitoring, maintenance and on-call cover around the clock.
PGXpertise™
Senior Postgres expertise on retainer — advice, reviews and second opinions when you need them.
Flex Consulting™
Scoped, outcome-driven project work — tuning, migrations, HA design and strategic planning.
Development
Custom development on and for PostgreSQL — extensions, patches and bespoke tooling.
PGX Longevity™
Continued support for end-of-life Postgres versions, on your timeline rather than the calendar's.
The team you hire to be sure.
Experienced
Decades on the hardest Postgres problems — corruption, recovery, scale. We have seen it before.
Reliable
24Ă—7 coverage and calm, methodical engagements. Uptime is the product; we treat it that way.
Sophisticated
Strategic data planning that fits your architecture and your business — not a template.
The latest from PGX.
Recent Talks
Language is a Virus: Locales and PostgreSQL
Christophe Pettus, March 6, 2025 · Southern California Linux Expo 2025
PGX on Social Media
PostgreSQL 19 is planned for general availability on Thursday, November 19. RC 2 shipped with last week's minor releases and there has been no RC 3. www.postgresql.org/developer/ro... pgexperts.com #PostgreSQL
— PGX (@pgexperts.bsky.social) 2026-11-17T15:33:04.338Z
Latest Commit
18 November 2026 07:06 UTC
Fix temporary relation I/O statistics in single-user mode
Accessing temporary relations in single-user mode could trigger an assertion failure in assertion-enabled builds. For example, CREATE TEMP TABLE AS and CREATE TEMP SEQUENCE failed when recording relation extension statistics. Without assertions, the statistics were still collected internally but were not exposed in pg_stat_io.
The problem was that pgstat_tracks_io_object() incorrectly excluded standalone backends from I/O tracking for temporary relations, even though they use local buffers just like regular client backends.
Remove this exclusion to prevent the assertion failures and make the statistics visible in pg_stat_io.
Backpatch to v16, where the incorrect exclusion was introduced in commit 28e626bde00.
- Author: Manuel Reyes Bravo [email protected]
- Reviewed-by: Fujii Masao [email protected]
- Discussion
- Backpatch-through: 16
PostgreSQL News
18 November 2026 07:00 UTC
Nikolay Samokhvalov: The hidden costs of CREATE TEMP TABLE: catalog bloat and LWLock:SInvalWrite
17 November 2026 22:00 UTC
Kaarel Moppel: A public safety reminder - large Postgres instances love huge pages
Nothing new for the Postgres veterans out there - basically a TLDR can be drawn from the title already. So here just my contribution to making the...
17 November 2026 15:00 UTC
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...
news feed via Planet PostgreSQL.
Have a Postgres problem? Let's talk.
From a one-off emergency to a long-term support plan — tell us what you need.
