PostgreSQL: JSON_TABLE Error Cascade, Join Fix and Test Flakiness

Three unrelated correctness fixes landed with no single pattern, headlined by an intentional SQL-standard change so table-level ERROR ON ERROR in JSON_TABLE now propagates to columns. A join-removal assertion fix back-patched to v16 and a test-isolation fix for intermittent buildfarm plan changes round out the activity.

Duration: PT2M18S

Episode overview

This episode is a short developer briefing from PostgreSQL.

It explains recent repository work in plain language.

  • Show: PostgreSQL
  • Published: 2026-09-20T13:04:09Z
  • Audio duration: PT2M18S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's Sunday, September twentieth, twenty twenty-six. You're listening to your PostgreSQL developer briefing.

Lead insight: No single theme today — three independent correctness fixes, with one intentional behavior change to JSON Table handling that you will need to account for.

First, standards compliance for JSON Table. In commit e73841f, table-level error handling now cascades down to columns, matching the SQL standard. Previously, a column without its own error clause always defaulted to returning null on error, even if the table specified error on error. That meant a query that should…

Second, a planner reliability fix for join removal. Commit a8bb1a7 resolves an assertion failure when a removed join is referenced through an alias. The parser keeps a syntactic reference to the join, even though the underlying data comes from a base table. The cleanup logic was stripping that reference and tripping…

Finally, test isolation. Commit 9e17d25 addresses intermittent plan changes in window and equivalence class tests. A foreign key test created a custom operator family using built-in integer operators, which became visible to concurrently running tests. The fix runs that…

Wh…

Nearby episodes from PostgreSQL

  1. Correctness Fixes Across Planner, Replication, and Foreign Keys
  2. Correctness Fixes Land Ahead of Version 19
  3. Tightening Up Before Release
  4. Table Access and REPACK Reliability
  5. Correctness Fixes Across Storage and Concurrency
  6. Version 19 Cleanup and Correctness Fixes
  7. Weekly Recap - Correctness Fixes and Replication Safety
  8. Hardening the Wait For LSN Feature