PostgreSQL 10 Open Items

From PostgreSQL wiki

Jump to: navigation, search

Contents

Open Issues

Decisions to Recheck Mid-Beta

  • Add migration instructions encouraging migration from MD5 to SCRAM once we know the state of drivers; see post

Older Bugs

  • GatherMerge is not hooked up to ExecReScan
    • original commit: 355d399 (principal author: Rushabh Lathia; owner: Robert Haas notified)
    • Fixed by commits 1295a777882b8ed180a854e249f91be565a99422 and a2b70c89ca1a5fcf6181d3c777d82e7b83d2de1b
    • ... um, no, still broken. It appears the main remaining issue is a pre-v10 problem: parallelism just doesn't work right with rescans.

Non-bugs

Resolved Issues

resolved before 10beta1


    • original commit: 7b504eb (principal author: Tomas Vondra; owner: Alvaro Herrera notified)
    • Fixed by commit 8c5cdb7f4f6e1d6a6104cb58ce4f23453891651b
  • SASLprep
    • Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8
  • pg_dump and SUBSCRIPTIONS
    • fixed by commits c31671f9b5f6eee9b6726baad2db1795c94839d1, a9254e675bde7dc2d976d207450c559d914c0dd6
  • synchronous_standby_names shows unused priority values
    • original commit: 3901fd7 (principal author: Masahiko Sawada; owner: Fujii Masao notified)
    • The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.
    • Not a bug. Consensus against current design; no consensus on which replacement to adopt. Need to resolve that debate.
    • Fixed by commit 346199dcab4cfb2c023373fb3d859583b59810d7
  • Rename wal location functions to "lsn"
    • Backward compatibility is already broken for most of these functions during the xlog to wal rename, and it'll likely be too late to change this once beta1 is out.
    • patch exists
    • fixed by commit d10c626de47d8b048b663471c7785603a2ec8641
  • snapshot builder has bugs
    • fixed by commits 2bef06d51646058c6bb480fcdbffb1f0cc914fed, 56e19d938dd1457ae078304df1b9903509a0a2bf, 955a684e0401954a58e956535107bc4b7136d952 and 524dbc14335cde0b18745f05a9112436d212f061

resolved before 10beta2

  • logical replication and PANIC during shutdown checkpoint in publisher
    • fixed in 2017-06-05 Freund commits
    • Also affects v9.4-v9.6 but v10 can trigger it from more places
    • major part fixed by commit 086221cf6b1727c2baed4703c582f657b7c5350e, but that commit had weaknesses
      • namely, HOT pruning during logical decoding might generate WAL
    • alternative patches exist
  • Query fails when SRFs are part of FROM clause
    • original commit: 69f4b9c (principal author: Tom Lane; owner: Andres Freund notified)
    • owner proposes classifying this as a non-bug
    • Really this is a variant of the SRF-inside-CASE issue, and was resolved by decision to treat that as an error
    • hence, fixed by commit 0436f6bde8848b7135f19dd7f8548b8c2ae89a34

resolved before 10beta3

resolved before 10beta4

Important Dates

Current schedule:

  • feature freeze: April 7th
  • beta1: wrap May 15th, announce May 18th
  • beta2: wrap July 10th, announce July 13th
  • beta3: wrap August 7th, announce August 10th

References:

Personal tools