PostgreSQL 18 Open Items

Open Issues

NOTE: Please place new open items at the end of the list.

NOTE: If known, please list the Owner of the open item.

• Split OAuth support from libpq into libpq-oauth
  • Owner: Daniel Gustafsson
  • Commit: b3f0be788afc17d2206e1ae1c731d8aeda1f2f59
  • Federated Authn/z with OAUTHBEARER

• Use extended stats for precise estimation of bucket size in hash join
  • Owner: Alexander Korotkov
  • Commit: 6bb6a62f3cc45624c601d5270673a17447734629
  • ERROR: corrupt MVNDistinct entry - 2

• Not null not valid: pg_dump output is inconsistent on table inheritence tables
  • Commit: a379061a22a8fdf421e1a457cc6af8503def6252
  • pg_dump not null not valid is wrong

• Doc: mention ALTER TABLE ADD COLUMN no need rewrite when column is virtual generated column
  • Commit: 11bd8318602fc2282a6201f714c15461dc2009c6
  • DOC: ALTER TABLE ADD COLUMN TABLE REWRITE

• self-join elimination
  • Owner: Alexander Korotkov
  • Commit: fc069a3a6319b5bf40d2f0f1efceae1c9b7a68a8
  • Some problems regarding the self-join elimination code
  • ERROR: too late to create a new PlaceHolderInfo

• Clean up injection point tests in AIO code
  • Owner: Andres Freund (note from Michael Paquier: I'm OK to handle this one).
  • Commit: 93bc3d75d8e1
  • Support for runtime parameters in injection points, for AIO tests

• Treat oauth_client_secret as a password in UIs
  • Owner: Jacob Champion
  • Commit: b3f0be788afc17d2206e1ae1c731d8aeda1f2f59
  • dispchar for oauth_client_secret

• Assertion failure in discardAbortedPipelineResults() with psql's pipeline mode
  • Owner: Michael Paquier
  • Commit :2cce0fe440fb
  • bug report
  • Proposal of patch

• Memory leak in parallel GIN builds
  • Owner: Tomas Vondra
  • Commit: 8492feb98f6df3f0f03e84ed56f0d1cbb2ac514c
  • bug report

• Fix guidance for running vacuumdb after pg_upgrade
  • Owner: Nathan Bossart
  • Commit: c9d502eb68
  • pgsql: Update guidance for running vacuumdb after pg_upgrade.

• Avoid core dump in pgstat_read_statsfile()
  • Owner: Michael Paquier
  • Commit: 7949d9594582
  • Avoid core dump in pgstat_read_statsfile()

Decisions to Recheck Mid-Beta

• Enable data checksums by default
  • Commit: 04bec894a0
  • Data checksums have been enabled by default. pg_upgrade cannot upgrade between non-checksum and checksum instances, so some additional steps are required by the user. Check whether the upgrade experience is tolerable and sufficiently documented. See the following list of threads that might be enhancing the end user experience:
    • Changing the state of data checksums in a running cluster

• fixing tsearch locale support
  • Commit: fb1a18810f0
  • Text search locale support has been updated and integrated into the common locale framework. Possible upgrade issues should probably at least be noted in the release notes.

• Enable statistics in pg_dump by default (Jeff Davis)?
  • Greg Sabino Mullane
  • Robert Haas

• decide what io_method to default to (Andres Freund)
  • Commit: 247ce06b883

Older bugs affecting stable branches

Live issues

• Incorrect results for (SP-)GIST index-only scans
  • GIST and SP-GIST indexes hold tuples in memory after releasing the pin on the page, but before returning them to the executor. This allows VACUUM to concurrently clean up any dead tuples from the page's results, and mark the heap pages that held the dead tuples as ALL_VISIBLE, breaking index-only scans.

• generation expression node collation inaccurate
  • generation expression node collation does not match the corresponding data type's collation

Fixed issues

• Incorrect results for bitmap heap scan.
  • Certain Bitmap Heap scans only test the visibility map before returning tuples. This can conflict with VACUUM removing tuples, thus causing more tuples to be returned from the scan than what are actually visible.
  • Commit: 459e7bf8e2

• bug in stored generated column over domain with constraints.
  • Commit: 7c872849407

Non-bugs

• Fundamental scheduling bug in parallel restore of partitioned tables
  • Current belief is that this is only a performance hazard, and hence not worth breaking feature freeze to fix. We can take it up in v19 instead.

Resolved Issues

resolved before 18beta1

• Difference in statistics on original and restored database
  • Owner: Ashutosh Bapat
  • Commit: 172259afb5
  • Original report
  • Fix discussion
  • Once this issue is fixed, we need to enable dumping statistics and comparing them in pg_upgrade/002_pg_upgrade.pl. The patch for the same is posted in the thread.

• Use-after-free with stats_fetch_consistency = snapshot and pg_stat_get_backend_wal()
  • Owner: Michael Paquier
  • Commit: 76def4cdd
  • Details of report
  • Fixed by: 3191a593d6de

• Performance regression in SQL-language functions
  • Owner: Tom Lane
  • Commit: 0dca5d68d
  • Performance issues with v18 SQL-language-function changes
  • Fixed by: 0400ae4a6 and four preceding patches

• Memory mismanagement leads to infinite loop in walsender
  • Owner: Tom Lane
  • Commit: 1afe31f03
  • bug report
  • Fixed by: 80b727eb9

• Not-null-in-pg_constraint changes cause parallel restore to deadlock
  • Owner: Alvaro Herrera
  • Commit: 14e87ffa5c543b5f30ead7413084c25f7735039f
  • Re: not null constraints, again
  • Fixed by: 11ff192b5

Won't Fix

• Rename --with-libcurl to --with-oauth-client
  • Owner: Jacob Champion
  • Commit: b3f0be788afc17d2206e1ae1c731d8aeda1f2f59
  • Federated Authn/z with OAUTHBEARER
  • This request was withdrawn, with input from Peter E and Robert.

Important Dates

Current schedule:

• Feature Freeze: April 8, 2025 0:00 AoE

See also

• Release Management Team
• PostgreSQL 17 Open Items