Difference between revisions of "PostgreSQL 13 Open Items"

From PostgreSQL wiki
Jump to: navigation, search
(Open Issues)
(Open Issues: Add open item about use of long data type in incremental sort code.)
Line 13: Line 13:
** Original commit: {{PgCommitURL|896ddf9b}}
** Original commit: {{PgCommitURL|896ddf9b}}
** Owner: Jeff Davis
** Owner: Jeff Davis
* [https://www.postgresql.org/message-id/CAApHDvpky+Uhof8mryPf5i=6e6fib2dxHqBrhp0Qhu0NeBhLJw@mail.gmail.com Incremental sort code uses long datatype for instrumentation for disk usage. sizeof(long) == 4 on windows 64-bit, i.e not big enough]
** Owner: James Coleman, Tomas Vondra
== Older Bugs ==
== Older Bugs ==

Revision as of 02:11, 31 July 2020

Open Issues

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

Older Bugs

Live issues

Fixed issues

Nothing to do


Resolved Issues

resolved before 13beta3

  • Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).

resolved before 13beta2

  • Should we rename effective_io_concurrency? It now has a different meaning and you might want to turn it up higher, though the default behaviour hasn't changed.
    • Commit: b09ff536
    • No one argued strongly in favour of changing it, so let's leave it as it is.

resolved before 13beta1

Won't Fix

Important Dates

Current schedule:

  • Feature Freeze: April 7, 2020 (Last Day to Commit Features)
  • Beta 1: May 21, 2020
  • Beta 2: June 25, 2020
  • Beta 3: August 13, 2020