PostgreSQL Experts for your business

PostgreSQL Experts, 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 service through database tuning and troubleshooting, to strategic data planning.

We offer a variety of support and consulting plans, tailored to the needs of organizations of any size, from small startups through Fortune 5 enterprises.

Let us know how we can help.

We've helped...

California Appellate Defense Counsel is a PGX client

... and dozens more.

PGX on Social Media

Christophe Pettus will be giving his new talk “Up Against the WAL: The Write-Ahead Log in PostgreSQL” at FOSSY 2025! We hope you’ll join him on Saturday August 2nd at 4:30pm PDT in Room 338! 2025.fossy.us/schedule/pre... @chanticleer.com #PostgreSQL #conference #Portland
— PGX (@pgexperts.bsky.social) 2025-07-10T13:09:17.550Z

Recent Talks

Language is a Virus: Locales and PostgreSQL

Christophe Pettus, March 6, 2025

Southern California Linux Expo 2025

Upcoming Event

FOSSY 2025, July 31-August 13, 2025

Smith Memorial Student Union
Portland State University
1825 SW Broadway
Portland, OR 97201

Latest Commit

11 July 2025 05:16 UTC

Fix the handling of two GUCs during upgrade.

Previously, the check_hook functions for max_slot_wal_keep_size and idle_replication_slot_timeout would incorrectly raise an ERROR for values set in postgresql.conf during upgrade, even though those values were not actively used in the upgrade process.

To prevent logical slot invalidation during upgrade, we used to set special values for these GUCs. Now, instead of relying on those values, we directly prevent WAL removal and logical slot invalidation caused by max_slot_wal_keep_size and idle_replication_slot_timeout.

Note: PostgreSQL 17 does not include the idle_replication_slot_timeout GUC, so related changes were not backported.

BUG #18979 * Reported-by: jorsol jorsol@gmail.com * Author: Dilip Kumar dilipbalaut@gmail.com Reviewed by: vignesh C vignesh21@gmail.com Reviewed by: Alvaro Herrera alvherre@alvh.no-ip.org * Backpatch-through: 17, where it was introduced * Discussion * Discussion

PostgreSQL News

10 July 2025 13:09 UTC