Difference between revisions of "PostgreSQL 10 Open Items"

From PostgreSQL wiki
Jump to: navigation, search
m (resolved before 10beta1)
m (Other)
Line 63: Line 63:
 
** original commit: {{PgCommitURL|3217327}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170414055644.GF2870454@tornado.leadboat.com|notified}})
 
** original commit: {{PgCommitURL|3217327}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170414055644.GF2870454@tornado.leadboat.com|notified}})
 
** Patch exists.
 
** Patch exists.
 
* [https://www.postgresql.org/message-id/CAMkU=1zMLnH_i1-PVQ-biZzvNx7VcuatriquEnh7HNk6K8Ss3Q@mail.gmail.com PANIC in pg_commit_ts slru after crashes, 2PC restore code at fault]
 
** Patch(es) exist(s).
 
  
 
== Design Decisions to Recheck Mid-Beta ==
 
== Design Decisions to Recheck Mid-Beta ==

Revision as of 11:08, 18 April 2017

Open Issues

Partitioning

Logical Replication

unless otherwise marked, original commit: 665d1fa (principal author: Petr Jelinek; owner: Peter Eisentraut)

SCRAM-SHA-256 Authentication

unless otherwise marked, original commit: 818fd4a (principal author: Michael Paquier; owner: Heikki Linnakangas)

Other

  • 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.

Design Decisions to Recheck Mid-Beta

Older Bugs

Non-bugs

Resolved Issues

resolved before 10beta1

  • SASLprep
    • Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8
  • pg_dump and SUBSCRIPTIONS
    • fixed by commits c31671f9b5f6eee9b6726baad2db1795c94839d1, a9254e675bde7dc2d976d207450c559d914c0dd6

Important Dates

Current schedule:

  • feature freeze: April 7th
  • beta1: wrap May 15th, announce May 18th

References: