Lately, the PostgreSQL’s bug-report mailing list has been receiving a large number of AI-generated bug reports.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
Stop Using AI to Report PostgreSQL Bugs
-
All Your GUCs in a Row: scram_iterations
`scram_iterations` embeds itself in each password when set and stays there forever, making it a per-password property masquerading as a server setting.
-
All Your GUCs in a Row: row_security
`row_security = off` doesn't disable row-level security—it triggers an error when a policy would apply.
-
All Your GUCs in a Row: restrict_nonsystem_relation_kind
PostgreSQL 16.4, 15.8, 14.13, 13.16 and 12.20 added a security parameter that only pg_dump uses.
-
All Your GUCs in a Row: restore_command
PostgreSQL's `restore_command` asks for WAL segments one at a time until the command fails—and that failure marks the archive's end, whether it's real or not.
-
All Your GUCs in a Row: restart_after_crash
When a PostgreSQL backend crashes, the postmaster can restart itself automatically or exit and wait for external intervention.
-
All Your GUCs in a Row: reserved_connections
PostgreSQL 16's `reserved_connections` reserves slots for your monitoring and backup roles when the application exhausts the pool.
-
All Your GUCs in a Row: remove_temp_files_after_crash
Protect your disk from orphaned temporary files after a backend crash.
-
All Your GUCs in a Row: recursive_worktable_factor
PostgreSQL 15's `recursive_worktable_factor` helps you fix slow recursive CTEs by tuning a single estimate.
-
All Your GUCs in a Row: the recovery_target parameters
Restore to the moment before the disaster using eight parameters that answer where replay stops, which timeline to follow, and what to do when you get there.
-
Binary read replicas in PostgreSQL, Part 3
Create replicas with a single command, but master the procedure for replacing a failed primary—that's where things get tricky and installations break.
-
All Your GUCs in a Row: recovery_prefetch
Standby lagging on network storage?
-
Binary read replicas in PostgreSQL, Part 2
Read replicas are one tool, but tuning a replica for one job and sending it another is a recipe for conflict.
-
All Your GUCs in a Row: recovery_min_apply_delay
recovery_min_apply_delay makes a standby late on purpose.
-
Binary read replicas in PostgreSQL, Part 1
A read replica is a PostgreSQL server in permanent recovery that accepts queries—and nearly every surprise it causes follows from that fact.
-
All Your GUCs in a Row: recovery_init_sync_method
After a crash, PostgreSQL syncs every file in your data directory before replaying any WAL—and on large clusters, this can consume minutes.
-
All Your GUCs in a Row: recovery_end_command
A hook that fires exactly once at promotion or restore completion—but the server is neither ready nor recovering while your command runs.
-
All Your GUCs in a Row: random_page_cost and seq_page_cost
The planner charges `random_page_cost` per index page based on how uncorrelated the index is—but the name lies.
-
All Your GUCs in a Row: quote_all_identifiers
Dumping across major versions?
-
All Your GUCs in a Row: primary_slot_name
Configure a replication slot name on your standby and the upstream keeps WAL forever—until the slot itself fills your disk or the standby dies holding an old…