· 3 min · PostgreSQL

All Your GUCs in a Row: check_function_bodies

PostgreSQL validates function bodies at creation time by default, catching syntax errors early.

0 comments

· 3 min · PostgreSQL

Table Access Methods Wake Up

PostgreSQL's Table Access Method API is finally seeing real action.

0 comments

· 3 min · PostgreSQL

All Your GUCs in a Row: bytea_output

PostgreSQL's `bytea_output` parameter controls how binary data is formatted when sent to clients: the modern `hex` format (default since 9.0) or the legacy…

0 comments

· 3 min · PostgreSQL

Patch PgBouncer Today

PgBouncer 1.25.2 shipped a patch for a pre-authentication crash (CVE-2026-6664). Any TCP connection can take down your pooler. Patch this week.

0 comments

· 3 min · PostgreSQL

All Your GUCs in a Row: bonjour and bonjour_name

PostgreSQL's Bonjour parameters let you advertise a server on the local network via Apple's service-discovery protocol—a clever 2002 idea that hasn't aged well.

0 comments

· 3 min · PostgreSQL

PostgreSQL 19 Beta: The Four Features You’ll Actually Feel

PostgreSQL 19 beta arrives with four operational game-changers: 64-bit MultiXact Members kill a decades-old "vacuum or die" failure mode, parallel autovacuum…

0 comments

· 3 min · PostgreSQL

All Your GUCs in a Row: block_size

A parameter you cannot change. block_size lives in the “Preset Options” section of the docs, alongside its read-only cousins like data_checksums, wal_block_size

0 comments

· 4 min · PostgreSQL

All Your GUCs in a Row: bgwriter_lru_maxpages and bgwriter_lru_multiplier

These two parameters close out the bgwriter cluster. Together with bgwriter_delay, they govern how the background writer decides what to write each round, and t

0 comments

· 4 min · PostgreSQL

All Your GUCs in a Row: bgwriter_delay and bgwriter_flush_after

The B cluster shifts gears: from one-off oddities to the background writer parameters, which span four GUCs. We do the first two as a pair because bgwriter_dela

0 comments

· 3 min · PostgreSQL

Two Decades, Two RCEs: What pgcrypto Has Been Doing Since 2005

Two remote code execution bugs lived in pgcrypto for twenty years until an AI fuzzer found them in a weekend. Here's what you need to know.

0 comments