https://wiki.postgresql.org/api.php?action=feedcontributions&user=Davidrowley&feedformat=atomPostgreSQL wiki - User contributions [en]2024-03-29T06:54:44ZUser contributionsMediaWiki 1.35.13https://wiki.postgresql.org/index.php?title=PostgreSQL_16_Open_Items&diff=38131PostgreSQL 16 Open Items2023-08-08T01:51:11Z<p>Davidrowley: Undo revision 38118 by Davidrowley (talk)</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
'''NOTE''': If known, please list the Owner of the open item.<br />
<br />
* {{messageLink|CAD21AoDvDmUQeJtZrau1ovnT_smN940%3DKp6mszNGK3bq9yRN6g%40mail.gmail.com| Performance degradation on concurrent COPY into a single relation in PG16 }}<br />
** Owner: Andres Freund<br />
* {{messageLink|36a6e89689716c2ca1fae8adc8e84601a041121c.camel@j-davis.com| Unexplained behavior when ICU rules is the empty string.}}<br />
** Owner: Peter Eisentraut<br />
* {{messageLink|CAMbWs496%2BN%3DUAjOc%3DrcD3P7B6oJe4rZw08e_TZRUsWbPxZW3Tw%40mail.gmail.com| Oversight in reparameterize_path_by_child leading to executor crash }}<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Add any items that need discussion here..<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer] [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report] [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report] [https://www.postgresql.org/message-id/flat/CAPH-tTxLf44s3CvUUtQpkDr1D8Hxqc2NGDzGXS1ODsfiJ6WSqA%40mail.gmail.com Another report] [https://www.postgresql.org/message-id/flat/a53cacb0-8835-57d6-31e4-4c5ef196de1a@deepbluecap.com Another report]<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/ZArVOMifjzE7f8W7%40paquier.xyz Requiring recovery.signal or standby.signal when recovering with a backup_label]<br />
** This is a rather old behavior that affects all stable branches, still not something that should be backpatched as-is.<br />
<br />
* {{messageLink|cfcca574-6967-c5ab-7dc3-2c82b6723b99@mail.ru|pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum}}<br />
** {{messageLink|1649062270.289865713@f403.i.mail.ru|Thread with patch}} [https://commitfest.postgresql.org/43/3739/ CF Entry]<br />
<br />
* {{messageLink|1516594.1681482708@sss.pgh.pa.us|We are not compatible with newly-released LLVM 16}}<br />
** {{messageLink|CA%2BhUKGKNX_%3Df%2B1C4r06WETKTq0G4Z_7q4L4Fxn5WWpMycDj9Fw%40mail.gmail.com|Patch}}<br />
** Owner: Thomas Munro (volunteer LLVM API change chaser)<br />
<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
** Fixed at: {{PgCommitURL|8fcb32db98eda1ad2a0c0b40b1cbb5d9a7aa68f0}} and {{PgCommitURL|ffd1b6bb6f8a2ffc929699772610c6925364dbb3}} for HEAD.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAC+AXB26a4EmxM2suXxPpJaGrqAdxracd7hskLg-zxtPB50h7A@mail.gmail.com Fix fseek() detection of unseekable files on WIN32]<br />
** Fixed at: {{PgCommitURL|a923e21631a29dc8b8781d7d02b5003d0df64ca3}} and {{PgCommitURL|765f5df726918bcdcfd16bcc5418e48663d1dd59}}, down to 14.<br />
<br />
* {{messageLink|CAAKRu_bETD%2BAri600h6fRjX2p8rJSeMAUp%3D_y88juqOZgouTSg%40mail.gmail.com|Can't disable autovacuum cost delay through storage parameter}}<br />
** Fixed at: {{PgCommitURL|bfac8f8bc4a44c67c9f35b5266676278e4ba1217}}, down to 11.<br />
<br />
* {{messageLink|CAJ7c6TMBTN3rcz4%3DAjYhLPD_w3FFT0Wq_C15jxCDn8U4tZnH1g@mail.gmail.com| EPQ misbehaves for inherited/partitioned tables}}<br />
** Fixed at: {{PgCommitURL|70b42f279}}, down to 14.<br />
<br />
* {{messageLink|ZEZDj1H61ryrmY9o@msg.df7cb.de|could not extend file "base/5/3501" with FileFallocate(): Interrupted system call}}<br />
** Original commit: {{PgCommitURL|4d330a61bb1}}<br />
** Fixed at: {{PgCommitURL|0d369ac650}}<br />
<br />
* {{messageLink|20230314174521.74jl6ffqsee5mtug%40awork3.anarazel.de|DROP DATABASE is interruptible}}<br />
** Additional discussion: {{messageLink|01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000%40eu-west-1.amazonses.com|"PANIC: could not open critical system index 2662" - twice}}<br />
** Fixed at: {{PgCommitURL|c66a7d75}}, down to 11.<br />
<br />
* {{messageLink|17997-a044c27aef95daf8@postgresql.org|Assertion failure when attaching a partition index}}<br />
** Fixed at: {{PgCommitURL|38ea6aa9}}, down to 11.<br />
** Fixed at: {{PgCommitURL|cfc43aeb}}, down to 11.<br />
<br />
* {{messageLink|ae46f2fb-5586-3de0-b54b-1bb0f6410ebd@inbox.ru|Issues with calculations of LimitAdditionalPins}}<br />
** Fixed at: {{PgCommitURL|bd2f46c6559}}<br />
<br />
== Non-bugs ==<br />
<br />
* {{messageLink|17862-1ab8f74b0f7b0611@postgresql.org|WindowAgg startup costs don't take into account partition bound. Can lead to incorrect use of cheap startup plans}}<br />
** {{messageLink|CAApHDvrB0S5BMv+0-wTTqWFE-BJ0noWqTnDu9QQfjZ2VSpLv_g@mail.gmail.com|Patch to fix and discussion}}<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 16beta3 ===<br />
* {{messageLink|CAJKUy5g2uZRrUDZJ8p-%3DgiwcSHVUn0c9nmdxPSY0jF0Ov8VoEA@mail.gmail.com|Assertion failure !bms_overlap(joinrel->relids, required_outer)}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|a798660ebe3ff1feb310db13b957c5cda4c8c50d}}<br />
* {{messageLink|ZJp921+nITFnvBVS@paquier.xyz|Add TLI number to name of files generated by pg_waldump --save-fullpage}}<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|b381d9637030c163c3b1f8a9d3de51dfc1b4ee58}}<br />
* {{messageLink|e587e2ee-7de0-88a2-10f8-c7cf001bab8c%40postgrespro.ru|psql: Add role's membership options to the \du+ command}}<br />
** Fixed at: {{PgCommitURL|0a1d2a7df852f16c452eef8a83003943125162c7}}<br />
* {{messageLink|ZKy4AdrLEfbqrxGJ@telsasoft.com|REINDEX segv on null pointer in RemoveFromWaitQueue}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|bd88404d3cda53810e0b0144713c4b1a1dd965a8}}<br />
<br />
=== resolved before 16beta2 ===<br />
* {{messageLink|17978-12f3d93a55297266@postgresql.org|wrong join order subsequent to removal of delay_upper_joins check}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|3af87736bf5d5c7bea086d962afc2bbf4f29279a}}<br />
* {{messageLink|DFBB2D25-DE97-49CA-A60E-07C881EA59A7@winand.at|Inconsistent nulling bitmap in nestloop parameters}}<br />
** Owner: Tom Lane<br />
** All known issues fixed as of {{PgCommitURL|efeb12ef0bfef0b5aa966a56bb4dbb1f936bda0c}}<br />
* {{messageLink|17976-4b638b525e9a983b@postgresql.org|join removal can no longer skip updating EquivalenceClasses}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|f4c00d138f6dea4c9d8af8ec280b7edc9b0a29e1}}<br />
* {{messageLink|CAH2-Wz%3D8Z9qY58bjm_7TAHgtW6RzZ5Ke62q5emdCEy9BAzwhmg%40mail.gmail.com|Cleaning up nbtree after logical decoding on standby work}}<br />
** Owner: Peter Geoghegan, Andres Freund<br />
** Original commit: {{PgCommitURL|61b313e4}}<br />
** Fixed at: {{PgCommitURL|d088ba5a}}<br />
* {{messageLink|CAMbWs4_tuVn9EwwMcggGiZJWWstdXX_ci8FeEU17vs+4nLgw3w@mail.gmail.com|Assert failure and wrong query results due to incorrectly removing PHV}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|9a2dbc614e6e47da3c49daacec106da32eba9467}}<br />
* {{messageLink|CAMbWs4-_vwkBij4XOQ5ukxUvLgwTm0kS5_DO9CicUeKbEfKjUw%40mail.gmail.com|Assert failure of the cross-check for nullingrels}}<br />
** Owner: Tom Lane<br />
** Original commit: {{PgCommitURL|2489d76c4}}<br />
** [https://commitfest.postgresql.org/43/4250/ CF Entry]<br />
** Fixed at: {{PgCommitURL|991a3df22}}<br />
* Switch to ICU for 17?<br />
** Owner: Jeff Davis<br />
** {{messageLink|82c4c816-06f6-d3e3-ba02-fca4a5cef065@enterprisedb.com|I suggest waiting until next week to commit it and then see what happens}}<br />
** [https://commitfest.postgresql.org/42/4169/ CF Entry]<br />
** Open item description not clear; if it is an open item, it's redundant with the issue "The rules for choosing default ICU locale seem pretty unfriendly". Closed. <br />
* {{messageLink|874jp9f5jo.fsf@news-spur.riddles.org.uk|The rules for choosing default ICU locale seem pretty unfriendly}}<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|2535c74b1a}}, {{PgCommitURL|f3a01af29b}}<br />
* {{messageLink|20230613211246.GA219055@nathanxps13|ff9618e creates cache lookup hazards with partition trees}}<br />
** Owner: Nathan Bossart, <s>Jeff Davis</s><br />
** Fixed at: {{PgCommitURL|4dbdb82513}}, {{PgCommitURL|c2122aae63}}<br />
=== resolved before 16beta1 ===<br />
* {{messageLink|CAHewXNnu7u1aT%3D%3DWjnCRa%2BSzKb6s80hvwPP_9eMvvvtdyFdqjw%40mail.gmail.com|ERROR: wrong varnullingrels (b 5 7) (expected (b)) for Var 3/3}}<br />
** Fixed at: {{PgCommitURL|d0f952691}}<br />
* {{messageLink|d46f9265-ff3c-6743-2278-6772598233c2%40pgmasters.net|Possible regression setting GUCs on \connect}}<br />
** Owner: Alexander Korotkov<br />
** Discussion on reverting {{PgCommitURL|096dd80f3}}<br />
** Original commit: {{PgCommitURL|096dd80f3}}<br />
** Reverted at: {{PgCommitURL|b9a7a822723aebb16cbe7e5fb874e5124745b07e}}<br />
<br />
* Planner makes improper clause pushdown decisions due to outer-join-aware-Vars changes<br />
** {{messageLink|0b819232-4b50-f245-1c7d-c8c61bf41827@postgrespro.ru|Clause accidentally pushed down}}<br />
** {{messageLink|CAHewXNks3w_Vy9CWoVtHx1XSaeiFpsOzh-zy5eu0Khp1PtG1sA@mail.gmail.com|wrong results due to qual pushdown}}<br />
** Original commit: {{PgCommitURL|2489d76c4}}<br />
** Fixed at: {{PgCommitURL|9df8f903eb6758be5a19e66cdf77e922e9329c31}}<br />
<br />
* Revert {{PgCommitURL|ec386948948}}, per {{messageLink|20230330105325.y6uvpalspynf2frt@alvherre.pgsql|Re: "variable not found in subplan target list"}}<br />
** Reverted at {{PgCommitURL|5472743d9e8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAEZATCWETioXs5kY8vT6BVguY41_wD962VDk%3Du_Nvd7S1UXzuQ%40mail.gmail.com ERROR: ORDER/GROUP BY expression not found in targetlist]<br />
** Fixed at: {{PgCommitURL|da5800d5fa636c6e10c9c98402d872c76aa1c8d0}}<br />
<br />
* [https://www.postgresql.org/message-id/20230212233711.GA1316@telsasoft.com various elogs hit by sqlsmith (ExecRTCheckPerms() and many prunable partitions)]<br />
** Fixed at: {{PgCommitURL|c7468c73f7b6e842a53c12eaee5578a76a8fa7a6}}<br />
<br />
* [https://www.postgresql.org/message-id/20230228235834.GC30529@telsasoft.com pg_dump: zlib compression fails for empty objects (LOs)]<br />
** Fixed at: {{PgCommitURL|00d9dcf5bebbb355152a60f0e2120cdf7f9e7ddd}}<br />
<br />
* [https://www.postgresql.org/message-id/20230227044910.GO1653@telsasoft.com pg_dump: lz4 compression uses no persistent state and writes a block header for every row]<br />
** Fixed at: {{PgCommitURL|0070b66fef21e909adb283f7faa7b1978836ad75}}<br />
<br />
* {{messageLink|3590249.1680971629@sss.pgh.pa.us|Assertion failure with parallel full hash join}}<br />
** Fixed at: {{PgCommitURL|b37d051b0e59e4324e346655a27509507813db79}}<br />
<br />
* {{messageLink|ZDDO6jaESKaBgej0@tamriel.snowman.net|De-revert "Add support for Kerberos credential delegation"}}<br />
** Owner: Stephen Frost<br />
** Original commit: {{PgCommitURL|3d4fa227bce4294ce1cc214b4a9d3b7caa3f0454}}<br />
** Revert: ({{PgCommitURL|3d03b24c350ab060bb223623bdff38835bd7afd0}}<br />
** De-Revert: {{PgCommitURL|6633cfb21691840c33816a6dacaca0b504efb895}}<br />
** Resolved at: {{PgCommitURL|f7431bca8b0138bdbce7025871560d39119565a0}}<br />
<br />
* {{messageLink|c39be3c5-c1a5-1e33-1024-16f527e251a4@enterprisedb.com|SSL tests break on non-existing system CA pool}}<br />
** Fixed at: {{PgCommitURL|0b5d1fb36adda612bd3d5d032463a6eeb0729237}}<br />
<br />
* {{messageLink|CAD21AoBS7o6Ljt_vfqPQPf67AhzKu3fR0iqk8B%3DvVYczMugKMQ%40mail.gmail.com|VacuumUpdateCosts() logging condition incorrect for some initial values of vacuum_cost_delay}}<br />
** Fixed at: {{PgCommitURL|a9781ae11ba2fdb44a3a72c9a7ebb727140b25c5}}<br />
<br />
* {{messageLink|CA%2BhUKGJ-ZPJwKHVLbqye92-ZXeLoCHu5wJL6L6HhNP7FkJ%3DmeA%40mail.gmail.com|check_strxfrm_bug()}}<br />
** Owner: Thomas Munro<br />
** Fixed at: {{PgCommitURL|7d3d72b55edd1b7552a9a358991555994efab0e9}}<br />
<br />
* {{messageLink|20230317230930.nhsgk3qfk7f4axls%40awork3.anarazel.de|Should we remove vacuum_defer_cleanup_age?}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|1118cd37eb61e6a2428f457a8b2026a7bb3f801a}}<br />
<br />
* {{messageLink|2fefa454-5a70-2174-ddbf-4a0e41537139@gmail.com|Add two missing tests in 035_standby_logical_decoding.pl}}<br />
** Fixed at: {{PgCommitURL|376dc820531bafcbf105fff74c5b14c23d9950af}}<br />
** Fixed at: {{PgCommitURL|a6e04b1d20c2e9cece9b64bb5b36ebfdc3a9031b}}<br />
<br />
* {{messageLink|b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com|Performance regression due to SQLValueFunction removal}}<br />
** Fixed at: {{PgCommitURL|d8c3106bb60e4f87be595f241e173ba3c2b7aa2c}}<br />
<br />
* {{messageLink|20230419172326.dhgyo4wrrhulovt6%40awork3.anarazel.de|pg_stat_io not tracking smgrwriteback() is confusing}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|093e5c57d506783a95dd8feddd9a3f2651e1aeba}}<br />
<br />
* {{messageLink|ZFhCyn4Gm2eu60rB@paquier.xyz|Table data compression is broken with pg_dump --compress lz4}}<br />
** Owner: Tomas Vondra<br />
** Fixed at: {{PgCommitURL|1a05c1d252993b0a59c58a6daf91a2df9333044f}}<br />
<br />
* {{messageLink|94ae9bca-5ebb-1e68-bb7b-4f32e89fefbe@gmail.com|Valgrind unhappy with LZ4F code in pg_dump}}<br />
** Owner: Tomas Vondra<br />
** Fixed at: {{PgCommitURL|3c18d90f8907e53c3021fca13ad046133c480e4d}}<br />
<br />
* {{messageLink|20230509190247.3rrplhdgem6su6cg@awork3.anarazel.de|walsender performance regression due to logical decoding on standby changes}}<br />
** Owner: Andres Freund<br />
** Original commit: {{PgCommitURL|e101dfac}}<br />
** Fixed at: {{PgCommitURL|bc971f4025c378ce500d86597c34b0ef996d4d8c}}<br />
<br />
== Won't Fix ==<br />
<br />
* Is it OK that WL_SOCKET_ACCEPT is less fair on Windows than on Unix (and than the coding before 16) when there are multiple server sockets configured?<br />
** {{messageLink|CA%2BhUKG%2BA2dk29hr5zRP3HVJQ-_PncNJM6HVQ7aaYLXLRBZU-xw%40mail.gmail.com|WL_SOCKET_ACCEPT fairness on Windows}} has a (blind) patch to fix that, but would need a Windows hacker to test<br />
** Owner: Thomas Munro<br />
** Original commit: {{PgCommitURL|7389aad6}}<br />
** Issue reclassified as a non-critical improvement to be [https://commitfest.postgresql.org/43/4263/ considered for 17]<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Beta 3: (August 10, 2023)<br />
* Beta 2: June 29, 2023<br />
* Beta 1: May 25, 2023<br />
* Feature Freeze: April 8, 2023 0:00 AoE ('''Last Day to Commit Features''')<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
* [[PostgreSQL 15 Open Items]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_16_Open_Items&diff=38118PostgreSQL 16 Open Items2023-08-07T06:14:42Z<p>Davidrowley: Resolved "Performance degradation on concurrent COPY into a single relation in PG16"</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
'''NOTE''': If known, please list the Owner of the open item.<br />
<br />
* {{messageLink|36a6e89689716c2ca1fae8adc8e84601a041121c.camel@j-davis.com| Unexplained behavior when ICU rules is the empty string.}}<br />
** Owner: Peter Eisentraut<br />
* {{messageLink|CAMbWs496%2BN%3DUAjOc%3DrcD3P7B6oJe4rZw08e_TZRUsWbPxZW3Tw%40mail.gmail.com| Oversight in reparameterize_path_by_child leading to executor crash }}<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Add any items that need discussion here..<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer] [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report] [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report] [https://www.postgresql.org/message-id/flat/CAPH-tTxLf44s3CvUUtQpkDr1D8Hxqc2NGDzGXS1ODsfiJ6WSqA%40mail.gmail.com Another report] [https://www.postgresql.org/message-id/flat/a53cacb0-8835-57d6-31e4-4c5ef196de1a@deepbluecap.com Another report]<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/ZArVOMifjzE7f8W7%40paquier.xyz Requiring recovery.signal or standby.signal when recovering with a backup_label]<br />
** This is a rather old behavior that affects all stable branches, still not something that should be backpatched as-is.<br />
<br />
* {{messageLink|cfcca574-6967-c5ab-7dc3-2c82b6723b99@mail.ru|pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum}}<br />
** {{messageLink|1649062270.289865713@f403.i.mail.ru|Thread with patch}} [https://commitfest.postgresql.org/43/3739/ CF Entry]<br />
<br />
* {{messageLink|1516594.1681482708@sss.pgh.pa.us|We are not compatible with newly-released LLVM 16}}<br />
** {{messageLink|CA%2BhUKGKNX_%3Df%2B1C4r06WETKTq0G4Z_7q4L4Fxn5WWpMycDj9Fw%40mail.gmail.com|Patch}}<br />
** Owner: Thomas Munro (volunteer LLVM API change chaser)<br />
<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
** Fixed at: {{PgCommitURL|8fcb32db98eda1ad2a0c0b40b1cbb5d9a7aa68f0}} and {{PgCommitURL|ffd1b6bb6f8a2ffc929699772610c6925364dbb3}} for HEAD.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAC+AXB26a4EmxM2suXxPpJaGrqAdxracd7hskLg-zxtPB50h7A@mail.gmail.com Fix fseek() detection of unseekable files on WIN32]<br />
** Fixed at: {{PgCommitURL|a923e21631a29dc8b8781d7d02b5003d0df64ca3}} and {{PgCommitURL|765f5df726918bcdcfd16bcc5418e48663d1dd59}}, down to 14.<br />
<br />
* {{messageLink|CAAKRu_bETD%2BAri600h6fRjX2p8rJSeMAUp%3D_y88juqOZgouTSg%40mail.gmail.com|Can't disable autovacuum cost delay through storage parameter}}<br />
** Fixed at: {{PgCommitURL|bfac8f8bc4a44c67c9f35b5266676278e4ba1217}}, down to 11.<br />
<br />
* {{messageLink|CAJ7c6TMBTN3rcz4%3DAjYhLPD_w3FFT0Wq_C15jxCDn8U4tZnH1g@mail.gmail.com| EPQ misbehaves for inherited/partitioned tables}}<br />
** Fixed at: {{PgCommitURL|70b42f279}}, down to 14.<br />
<br />
* {{messageLink|ZEZDj1H61ryrmY9o@msg.df7cb.de|could not extend file "base/5/3501" with FileFallocate(): Interrupted system call}}<br />
** Original commit: {{PgCommitURL|4d330a61bb1}}<br />
** Fixed at: {{PgCommitURL|0d369ac650}}<br />
<br />
* {{messageLink|20230314174521.74jl6ffqsee5mtug%40awork3.anarazel.de|DROP DATABASE is interruptible}}<br />
** Additional discussion: {{messageLink|01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000%40eu-west-1.amazonses.com|"PANIC: could not open critical system index 2662" - twice}}<br />
** Fixed at: {{PgCommitURL|c66a7d75}}, down to 11.<br />
<br />
* {{messageLink|17997-a044c27aef95daf8@postgresql.org|Assertion failure when attaching a partition index}}<br />
** Fixed at: {{PgCommitURL|38ea6aa9}}, down to 11.<br />
** Fixed at: {{PgCommitURL|cfc43aeb}}, down to 11.<br />
<br />
* {{messageLink|ae46f2fb-5586-3de0-b54b-1bb0f6410ebd@inbox.ru|Issues with calculations of LimitAdditionalPins}}<br />
** Fixed at: {{PgCommitURL|bd2f46c6559}}<br />
<br />
== Non-bugs ==<br />
<br />
* {{messageLink|17862-1ab8f74b0f7b0611@postgresql.org|WindowAgg startup costs don't take into account partition bound. Can lead to incorrect use of cheap startup plans}}<br />
** {{messageLink|CAApHDvrB0S5BMv+0-wTTqWFE-BJ0noWqTnDu9QQfjZ2VSpLv_g@mail.gmail.com|Patch to fix and discussion}}<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 16beta3 ===<br />
* {{messageLink|CAJKUy5g2uZRrUDZJ8p-%3DgiwcSHVUn0c9nmdxPSY0jF0Ov8VoEA@mail.gmail.com|Assertion failure !bms_overlap(joinrel->relids, required_outer)}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|a798660ebe3ff1feb310db13b957c5cda4c8c50d}}<br />
* {{messageLink|ZJp921+nITFnvBVS@paquier.xyz|Add TLI number to name of files generated by pg_waldump --save-fullpage}}<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|b381d9637030c163c3b1f8a9d3de51dfc1b4ee58}}<br />
* {{messageLink|e587e2ee-7de0-88a2-10f8-c7cf001bab8c%40postgrespro.ru|psql: Add role's membership options to the \du+ command}}<br />
** Fixed at: {{PgCommitURL|0a1d2a7df852f16c452eef8a83003943125162c7}}<br />
* {{messageLink|ZKy4AdrLEfbqrxGJ@telsasoft.com|REINDEX segv on null pointer in RemoveFromWaitQueue}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|bd88404d3cda53810e0b0144713c4b1a1dd965a8}}<br />
* {{messageLink|CAD21AoDvDmUQeJtZrau1ovnT_smN940%3DKp6mszNGK3bq9yRN6g%40mail.gmail.com| Performance degradation on concurrent COPY into a single relation in PG16 }}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|c1308ce2d9224f0ec08128ab35e161837f9a5105}}<br />
** Fixed at: {{PgCommitURL|4e2e75cd29eb7bc591afe30fd7425629fe2c5a5d}}<br />
<br />
=== resolved before 16beta2 ===<br />
* {{messageLink|17978-12f3d93a55297266@postgresql.org|wrong join order subsequent to removal of delay_upper_joins check}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|3af87736bf5d5c7bea086d962afc2bbf4f29279a}}<br />
* {{messageLink|DFBB2D25-DE97-49CA-A60E-07C881EA59A7@winand.at|Inconsistent nulling bitmap in nestloop parameters}}<br />
** Owner: Tom Lane<br />
** All known issues fixed as of {{PgCommitURL|efeb12ef0bfef0b5aa966a56bb4dbb1f936bda0c}}<br />
* {{messageLink|17976-4b638b525e9a983b@postgresql.org|join removal can no longer skip updating EquivalenceClasses}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|f4c00d138f6dea4c9d8af8ec280b7edc9b0a29e1}}<br />
* {{messageLink|CAH2-Wz%3D8Z9qY58bjm_7TAHgtW6RzZ5Ke62q5emdCEy9BAzwhmg%40mail.gmail.com|Cleaning up nbtree after logical decoding on standby work}}<br />
** Owner: Peter Geoghegan, Andres Freund<br />
** Original commit: {{PgCommitURL|61b313e4}}<br />
** Fixed at: {{PgCommitURL|d088ba5a}}<br />
* {{messageLink|CAMbWs4_tuVn9EwwMcggGiZJWWstdXX_ci8FeEU17vs+4nLgw3w@mail.gmail.com|Assert failure and wrong query results due to incorrectly removing PHV}}<br />
** Owner: Tom Lane<br />
** Fixed at: {{PgCommitURL|9a2dbc614e6e47da3c49daacec106da32eba9467}}<br />
* {{messageLink|CAMbWs4-_vwkBij4XOQ5ukxUvLgwTm0kS5_DO9CicUeKbEfKjUw%40mail.gmail.com|Assert failure of the cross-check for nullingrels}}<br />
** Owner: Tom Lane<br />
** Original commit: {{PgCommitURL|2489d76c4}}<br />
** [https://commitfest.postgresql.org/43/4250/ CF Entry]<br />
** Fixed at: {{PgCommitURL|991a3df22}}<br />
* Switch to ICU for 17?<br />
** Owner: Jeff Davis<br />
** {{messageLink|82c4c816-06f6-d3e3-ba02-fca4a5cef065@enterprisedb.com|I suggest waiting until next week to commit it and then see what happens}}<br />
** [https://commitfest.postgresql.org/42/4169/ CF Entry]<br />
** Open item description not clear; if it is an open item, it's redundant with the issue "The rules for choosing default ICU locale seem pretty unfriendly". Closed. <br />
* {{messageLink|874jp9f5jo.fsf@news-spur.riddles.org.uk|The rules for choosing default ICU locale seem pretty unfriendly}}<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|2535c74b1a}}, {{PgCommitURL|f3a01af29b}}<br />
* {{messageLink|20230613211246.GA219055@nathanxps13|ff9618e creates cache lookup hazards with partition trees}}<br />
** Owner: Nathan Bossart, <s>Jeff Davis</s><br />
** Fixed at: {{PgCommitURL|4dbdb82513}}, {{PgCommitURL|c2122aae63}}<br />
=== resolved before 16beta1 ===<br />
* {{messageLink|CAHewXNnu7u1aT%3D%3DWjnCRa%2BSzKb6s80hvwPP_9eMvvvtdyFdqjw%40mail.gmail.com|ERROR: wrong varnullingrels (b 5 7) (expected (b)) for Var 3/3}}<br />
** Fixed at: {{PgCommitURL|d0f952691}}<br />
* {{messageLink|d46f9265-ff3c-6743-2278-6772598233c2%40pgmasters.net|Possible regression setting GUCs on \connect}}<br />
** Owner: Alexander Korotkov<br />
** Discussion on reverting {{PgCommitURL|096dd80f3}}<br />
** Original commit: {{PgCommitURL|096dd80f3}}<br />
** Reverted at: {{PgCommitURL|b9a7a822723aebb16cbe7e5fb874e5124745b07e}}<br />
<br />
* Planner makes improper clause pushdown decisions due to outer-join-aware-Vars changes<br />
** {{messageLink|0b819232-4b50-f245-1c7d-c8c61bf41827@postgrespro.ru|Clause accidentally pushed down}}<br />
** {{messageLink|CAHewXNks3w_Vy9CWoVtHx1XSaeiFpsOzh-zy5eu0Khp1PtG1sA@mail.gmail.com|wrong results due to qual pushdown}}<br />
** Original commit: {{PgCommitURL|2489d76c4}}<br />
** Fixed at: {{PgCommitURL|9df8f903eb6758be5a19e66cdf77e922e9329c31}}<br />
<br />
* Revert {{PgCommitURL|ec386948948}}, per {{messageLink|20230330105325.y6uvpalspynf2frt@alvherre.pgsql|Re: "variable not found in subplan target list"}}<br />
** Reverted at {{PgCommitURL|5472743d9e8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAEZATCWETioXs5kY8vT6BVguY41_wD962VDk%3Du_Nvd7S1UXzuQ%40mail.gmail.com ERROR: ORDER/GROUP BY expression not found in targetlist]<br />
** Fixed at: {{PgCommitURL|da5800d5fa636c6e10c9c98402d872c76aa1c8d0}}<br />
<br />
* [https://www.postgresql.org/message-id/20230212233711.GA1316@telsasoft.com various elogs hit by sqlsmith (ExecRTCheckPerms() and many prunable partitions)]<br />
** Fixed at: {{PgCommitURL|c7468c73f7b6e842a53c12eaee5578a76a8fa7a6}}<br />
<br />
* [https://www.postgresql.org/message-id/20230228235834.GC30529@telsasoft.com pg_dump: zlib compression fails for empty objects (LOs)]<br />
** Fixed at: {{PgCommitURL|00d9dcf5bebbb355152a60f0e2120cdf7f9e7ddd}}<br />
<br />
* [https://www.postgresql.org/message-id/20230227044910.GO1653@telsasoft.com pg_dump: lz4 compression uses no persistent state and writes a block header for every row]<br />
** Fixed at: {{PgCommitURL|0070b66fef21e909adb283f7faa7b1978836ad75}}<br />
<br />
* {{messageLink|3590249.1680971629@sss.pgh.pa.us|Assertion failure with parallel full hash join}}<br />
** Fixed at: {{PgCommitURL|b37d051b0e59e4324e346655a27509507813db79}}<br />
<br />
* {{messageLink|ZDDO6jaESKaBgej0@tamriel.snowman.net|De-revert "Add support for Kerberos credential delegation"}}<br />
** Owner: Stephen Frost<br />
** Original commit: {{PgCommitURL|3d4fa227bce4294ce1cc214b4a9d3b7caa3f0454}}<br />
** Revert: ({{PgCommitURL|3d03b24c350ab060bb223623bdff38835bd7afd0}}<br />
** De-Revert: {{PgCommitURL|6633cfb21691840c33816a6dacaca0b504efb895}}<br />
** Resolved at: {{PgCommitURL|f7431bca8b0138bdbce7025871560d39119565a0}}<br />
<br />
* {{messageLink|c39be3c5-c1a5-1e33-1024-16f527e251a4@enterprisedb.com|SSL tests break on non-existing system CA pool}}<br />
** Fixed at: {{PgCommitURL|0b5d1fb36adda612bd3d5d032463a6eeb0729237}}<br />
<br />
* {{messageLink|CAD21AoBS7o6Ljt_vfqPQPf67AhzKu3fR0iqk8B%3DvVYczMugKMQ%40mail.gmail.com|VacuumUpdateCosts() logging condition incorrect for some initial values of vacuum_cost_delay}}<br />
** Fixed at: {{PgCommitURL|a9781ae11ba2fdb44a3a72c9a7ebb727140b25c5}}<br />
<br />
* {{messageLink|CA%2BhUKGJ-ZPJwKHVLbqye92-ZXeLoCHu5wJL6L6HhNP7FkJ%3DmeA%40mail.gmail.com|check_strxfrm_bug()}}<br />
** Owner: Thomas Munro<br />
** Fixed at: {{PgCommitURL|7d3d72b55edd1b7552a9a358991555994efab0e9}}<br />
<br />
* {{messageLink|20230317230930.nhsgk3qfk7f4axls%40awork3.anarazel.de|Should we remove vacuum_defer_cleanup_age?}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|1118cd37eb61e6a2428f457a8b2026a7bb3f801a}}<br />
<br />
* {{messageLink|2fefa454-5a70-2174-ddbf-4a0e41537139@gmail.com|Add two missing tests in 035_standby_logical_decoding.pl}}<br />
** Fixed at: {{PgCommitURL|376dc820531bafcbf105fff74c5b14c23d9950af}}<br />
** Fixed at: {{PgCommitURL|a6e04b1d20c2e9cece9b64bb5b36ebfdc3a9031b}}<br />
<br />
* {{messageLink|b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com|Performance regression due to SQLValueFunction removal}}<br />
** Fixed at: {{PgCommitURL|d8c3106bb60e4f87be595f241e173ba3c2b7aa2c}}<br />
<br />
* {{messageLink|20230419172326.dhgyo4wrrhulovt6%40awork3.anarazel.de|pg_stat_io not tracking smgrwriteback() is confusing}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|093e5c57d506783a95dd8feddd9a3f2651e1aeba}}<br />
<br />
* {{messageLink|ZFhCyn4Gm2eu60rB@paquier.xyz|Table data compression is broken with pg_dump --compress lz4}}<br />
** Owner: Tomas Vondra<br />
** Fixed at: {{PgCommitURL|1a05c1d252993b0a59c58a6daf91a2df9333044f}}<br />
<br />
* {{messageLink|94ae9bca-5ebb-1e68-bb7b-4f32e89fefbe@gmail.com|Valgrind unhappy with LZ4F code in pg_dump}}<br />
** Owner: Tomas Vondra<br />
** Fixed at: {{PgCommitURL|3c18d90f8907e53c3021fca13ad046133c480e4d}}<br />
<br />
* {{messageLink|20230509190247.3rrplhdgem6su6cg@awork3.anarazel.de|walsender performance regression due to logical decoding on standby changes}}<br />
** Owner: Andres Freund<br />
** Original commit: {{PgCommitURL|e101dfac}}<br />
** Fixed at: {{PgCommitURL|bc971f4025c378ce500d86597c34b0ef996d4d8c}}<br />
<br />
== Won't Fix ==<br />
<br />
* Is it OK that WL_SOCKET_ACCEPT is less fair on Windows than on Unix (and than the coding before 16) when there are multiple server sockets configured?<br />
** {{messageLink|CA%2BhUKG%2BA2dk29hr5zRP3HVJQ-_PncNJM6HVQ7aaYLXLRBZU-xw%40mail.gmail.com|WL_SOCKET_ACCEPT fairness on Windows}} has a (blind) patch to fix that, but would need a Windows hacker to test<br />
** Owner: Thomas Munro<br />
** Original commit: {{PgCommitURL|7389aad6}}<br />
** Issue reclassified as a non-critical improvement to be [https://commitfest.postgresql.org/43/4263/ considered for 17]<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Beta 3: (August 10, 2023)<br />
* Beta 2: June 29, 2023<br />
* Beta 1: May 25, 2023<br />
* Feature Freeze: April 8, 2023 0:00 AoE ('''Last Day to Commit Features''')<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
* [[PostgreSQL 15 Open Items]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_16_Open_Items&diff=37916PostgreSQL 16 Open Items2023-05-31T01:01:16Z<p>Davidrowley: Moved "WindowAgg startup costs don't take into account partition bound" to non-bugs</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
'''NOTE''': If known, please list the Owner of the open item.<br />
<br />
* Switch to ICU for 17?<br />
** Owner: Jeff Davis<br />
** {{messageLink|82c4c816-06f6-d3e3-ba02-fca4a5cef065@enterprisedb.com|I suggest waiting until next week to commit it and then see what happens}}<br />
** [https://commitfest.postgresql.org/42/4169/ CF Entry]<br />
* {{messageLink|e587e2ee-7de0-88a2-10f8-c7cf001bab8c%40postgrespro.ru|psql: Add role's membership options to the \du+ command}}<br />
** [https://commitfest.postgresql.org/43/4116/ CF Entry]<br />
** NOTE: This is not a committed feature for v16<br />
* {{messageLink|874jp9f5jo.fsf@news-spur.riddles.org.uk|The rules for choosing default ICU locale seem pretty unfriendly}}<br />
** Owner: Jeff Davis<br />
* {{messageLink|CAMbWs4-_vwkBij4XOQ5ukxUvLgwTm0kS5_DO9CicUeKbEfKjUw%40mail.gmail.com|Assert failure of the cross-check for nullingrels}}<br />
** Owner: Tom Lane<br />
** Original commit: {{PgCommitURL|2489d76c4}}<br />
** [https://commitfest.postgresql.org/43/4250/ CF Entry]<br />
* {{messageLink|ZEZDj1H61ryrmY9o@msg.df7cb.de|could not extend file "base/5/3501" with FileFallocate(): Interrupted system call}}<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/268fd337-8bb7-92e6-0da2-416c022c11f3%40enterprisedb.com Reconsider a utility_query_id GUC to control if query jumbling of utilities can go through the past string-only mode and the new mode?]<br />
** Potential owner: Michael Paquier<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer] [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report] [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report] [https://www.postgresql.org/message-id/flat/CAPH-tTxLf44s3CvUUtQpkDr1D8Hxqc2NGDzGXS1ODsfiJ6WSqA%40mail.gmail.com Another report] [https://www.postgresql.org/message-id/flat/a53cacb0-8835-57d6-31e4-4c5ef196de1a@deepbluecap.com Another report]<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/ZArVOMifjzE7f8W7%40paquier.xyz Requiring recovery.signal or standby.signal when recovering with a backup_label]<br />
** This is a rather old behavior that affects all stable branches, still not something that should be backpatched as-is.<br />
<br />
* {{messageLink|cfcca574-6967-c5ab-7dc3-2c82b6723b99@mail.ru|pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum}}<br />
** {{messageLink|1649062270.289865713@f403.i.mail.ru|Thread with patch}} [https://commitfest.postgresql.org/43/3739/ CF Entry]<br />
<br />
* {{messageLink|1516594.1681482708@sss.pgh.pa.us|We are not compatible with newly-released LLVM 16}}<br />
** {{messageLink|CA%2BhUKGKNX_%3Df%2B1C4r06WETKTq0G4Z_7q4L4Fxn5WWpMycDj9Fw%40mail.gmail.com|Patch}}<br />
** Owner: Thomas Munro (volunteer LLVM API change chaser)<br />
<br />
* {{messageLink|20230314174521.74jl6ffqsee5mtug%40awork3.anarazel.de|DROP DATABASE is interruptible}}<br />
** Additional discussion: {{messageLink|01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000%40eu-west-1.amazonses.com|"PANIC: could not open critical system index 2662" - twice}}<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
** Fixed at: {{PgCommitURL|8fcb32db98eda1ad2a0c0b40b1cbb5d9a7aa68f0}} and {{PgCommitURL|ffd1b6bb6f8a2ffc929699772610c6925364dbb3}} for HEAD.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAC+AXB26a4EmxM2suXxPpJaGrqAdxracd7hskLg-zxtPB50h7A@mail.gmail.com Fix fseek() detection of unseekable files on WIN32]<br />
** Fixed at: {{PgCommitURL|a923e21631a29dc8b8781d7d02b5003d0df64ca3}} and {{PgCommitURL|765f5df726918bcdcfd16bcc5418e48663d1dd59}}, down to 14.<br />
<br />
* {{messageLink|CAAKRu_bETD%2BAri600h6fRjX2p8rJSeMAUp%3D_y88juqOZgouTSg%40mail.gmail.com|Can't disable autovacuum cost delay through storage parameter}}<br />
** Fixed at: {{PgCommitURL|bfac8f8bc4a44c67c9f35b5266676278e4ba1217}}, down to 11.<br />
<br />
* {{messageLink|CAJ7c6TMBTN3rcz4%3DAjYhLPD_w3FFT0Wq_C15jxCDn8U4tZnH1g@mail.gmail.com| EPQ misbehaves for inherited/partitioned tables}}<br />
** Fixed at: {{PgCommitURL|70b42f279}}, down to 14.<br />
<br />
== Non-bugs ==<br />
<br />
* {{messageLink|17862-1ab8f74b0f7b0611@postgresql.org|WindowAgg startup costs don't take into account partition bound. Can lead to incorrect use of cheap startup plans}}<br />
** {{messageLink|CAApHDvrB0S5BMv+0-wTTqWFE-BJ0noWqTnDu9QQfjZ2VSpLv_g@mail.gmail.com|Patch to fix and discussion}}<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 16beta2 ===<br />
<br />
=== resolved before 16beta1 ===<br />
<br />
* {{messageLink|CAHewXNnu7u1aT%3D%3DWjnCRa%2BSzKb6s80hvwPP_9eMvvvtdyFdqjw%40mail.gmail.com|ERROR: wrong varnullingrels (b 5 7) (expected (b)) for Var 3/3}}<br />
** Fixed at: {{PgCommitURL|d0f952691}}<br />
* {{messageLink|d46f9265-ff3c-6743-2278-6772598233c2%40pgmasters.net|Possible regression setting GUCs on \connect}}<br />
** Owner: Alexander Korotkov<br />
** Discussion on reverting {{PgCommitURL|096dd80f3}}<br />
** Original commit: {{PgCommitURL|096dd80f3}}<br />
** Reverted at: {{PgCommitURL|b9a7a822723aebb16cbe7e5fb874e5124745b07e}}<br />
<br />
* Planner makes improper clause pushdown decisions due to outer-join-aware-Vars changes<br />
** {{messageLink|0b819232-4b50-f245-1c7d-c8c61bf41827@postgrespro.ru|Clause accidentally pushed down}}<br />
** {{messageLink|CAHewXNks3w_Vy9CWoVtHx1XSaeiFpsOzh-zy5eu0Khp1PtG1sA@mail.gmail.com|wrong results due to qual pushdown}}<br />
** Original commit: {{PgCommitURL|2489d76c4}}<br />
** Fixed at: {{PgCommitURL|9df8f903eb6758be5a19e66cdf77e922e9329c31}}<br />
<br />
* Revert {{PgCommitURL|ec386948948}}, per {{messageLink|20230330105325.y6uvpalspynf2frt@alvherre.pgsql|Re: "variable not found in subplan target list"}}<br />
** Reverted at {{PgCommitURL|5472743d9e8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAEZATCWETioXs5kY8vT6BVguY41_wD962VDk%3Du_Nvd7S1UXzuQ%40mail.gmail.com ERROR: ORDER/GROUP BY expression not found in targetlist]<br />
** Fixed at: {{PgCommitURL|da5800d5fa636c6e10c9c98402d872c76aa1c8d0}}<br />
<br />
* [https://www.postgresql.org/message-id/20230212233711.GA1316@telsasoft.com various elogs hit by sqlsmith (ExecRTCheckPerms() and many prunable partitions)]<br />
** Fixed at: {{PgCommitURL|c7468c73f7b6e842a53c12eaee5578a76a8fa7a6}}<br />
<br />
* [https://www.postgresql.org/message-id/20230228235834.GC30529@telsasoft.com pg_dump: zlib compression fails for empty objects (LOs)]<br />
** Fixed at: {{PgCommitURL|00d9dcf5bebbb355152a60f0e2120cdf7f9e7ddd}}<br />
<br />
* [https://www.postgresql.org/message-id/20230227044910.GO1653@telsasoft.com pg_dump: lz4 compression uses no persistent state and writes a block header for every row]<br />
** Fixed at: {{PgCommitURL|0070b66fef21e909adb283f7faa7b1978836ad75}}<br />
<br />
* {{messageLink|3590249.1680971629@sss.pgh.pa.us|Assertion failure with parallel full hash join}}<br />
** Fixed at: {{PgCommitURL|b37d051b0e59e4324e346655a27509507813db79}}<br />
<br />
* {{messageLink|ZDDO6jaESKaBgej0@tamriel.snowman.net|De-revert "Add support for Kerberos credential delegation"}}<br />
** Owner: Stephen Frost<br />
** Original commit: {{PgCommitURL|3d4fa227bce4294ce1cc214b4a9d3b7caa3f0454}}<br />
** Revert: ({{PgCommitURL|3d03b24c350ab060bb223623bdff38835bd7afd0}}<br />
** De-Revert: {{PgCommitURL|6633cfb21691840c33816a6dacaca0b504efb895}}<br />
** Resolved at: {{PgCommitURL|f7431bca8b0138bdbce7025871560d39119565a0}}<br />
<br />
* {{messageLink|c39be3c5-c1a5-1e33-1024-16f527e251a4@enterprisedb.com|SSL tests break on non-existing system CA pool}}<br />
** Fixed at: {{PgCommitURL|0b5d1fb36adda612bd3d5d032463a6eeb0729237}}<br />
<br />
* {{messageLink|CAD21AoBS7o6Ljt_vfqPQPf67AhzKu3fR0iqk8B%3DvVYczMugKMQ%40mail.gmail.com|VacuumUpdateCosts() logging condition incorrect for some initial values of vacuum_cost_delay}}<br />
** Fixed at: {{PgCommitURL|a9781ae11ba2fdb44a3a72c9a7ebb727140b25c5}}<br />
<br />
* {{messageLink|CA%2BhUKGJ-ZPJwKHVLbqye92-ZXeLoCHu5wJL6L6HhNP7FkJ%3DmeA%40mail.gmail.com|check_strxfrm_bug()}}<br />
** Owner: Thomas Munro<br />
** Fixed at: {{PgCommitURL|7d3d72b55edd1b7552a9a358991555994efab0e9}}<br />
<br />
* {{messageLink|20230317230930.nhsgk3qfk7f4axls%40awork3.anarazel.de|Should we remove vacuum_defer_cleanup_age?}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|1118cd37eb61e6a2428f457a8b2026a7bb3f801a}}<br />
<br />
* {{messageLink|2fefa454-5a70-2174-ddbf-4a0e41537139@gmail.com|Add two missing tests in 035_standby_logical_decoding.pl}}<br />
** Fixed at: {{PgCommitURL|376dc820531bafcbf105fff74c5b14c23d9950af}}<br />
** Fixed at: {{PgCommitURL|a6e04b1d20c2e9cece9b64bb5b36ebfdc3a9031b}}<br />
<br />
* {{messageLink|b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com|Performance regression due to SQLValueFunction removal}}<br />
** Fixed at: {{PgCommitURL|d8c3106bb60e4f87be595f241e173ba3c2b7aa2c}}<br />
<br />
* {{messageLink|20230419172326.dhgyo4wrrhulovt6%40awork3.anarazel.de|pg_stat_io not tracking smgrwriteback() is confusing}}<br />
** Owner: Andres Freund<br />
** Fixed at: {{PgCommitURL|093e5c57d506783a95dd8feddd9a3f2651e1aeba}}<br />
<br />
* {{messageLink|ZFhCyn4Gm2eu60rB@paquier.xyz|Table data compression is broken with pg_dump --compress lz4}}<br />
** Owner: Tomas Vondra<br />
** Fixed at: {{PgCommitURL|1a05c1d252993b0a59c58a6daf91a2df9333044f}}<br />
<br />
* {{messageLink|94ae9bca-5ebb-1e68-bb7b-4f32e89fefbe@gmail.com|Valgrind unhappy with LZ4F code in pg_dump}}<br />
** Owner: Tomas Vondra<br />
** Fixed at: {{PgCommitURL|3c18d90f8907e53c3021fca13ad046133c480e4d}}<br />
<br />
* {{messageLink|20230509190247.3rrplhdgem6su6cg@awork3.anarazel.de|walsender performance regression due to logical decoding on standby changes}}<br />
** Owner: Andres Freund<br />
** Original commit: {{PgCommitURL|e101dfac}}<br />
** Fixed at: {{PgCommitURL|bc971f4025c378ce500d86597c34b0ef996d4d8c}}<br />
<br />
== Won't Fix ==<br />
<br />
* Is it OK that WL_SOCKET_ACCEPT is less fair on Windows than on Unix (and than the coding before 16) when there are multiple server sockets configured?<br />
** {{messageLink|CA%2BhUKG%2BA2dk29hr5zRP3HVJQ-_PncNJM6HVQ7aaYLXLRBZU-xw%40mail.gmail.com|WL_SOCKET_ACCEPT fairness on Windows}} has a (blind) patch to fix that, but would need a Windows hacker to test<br />
** Owner: Thomas Munro<br />
** Original commit: {{PgCommitURL|7389aad6}}<br />
** Issue reclassified as a non-critical improvement to be [https://commitfest.postgresql.org/43/4263/ considered for 17]<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Beta 2: TBD<br />
* Beta 1: May 25, 2023<br />
* Feature Freeze: April 8, 2023 0:00 AoE ('''Last Day to Commit Features''')<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
* [[PostgreSQL 15 Open Items]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PgCon_2023_Developer_Meeting&diff=37870PgCon 2023 Developer Meeting2023-05-26T00:17:22Z<p>Davidrowley: /* RSVPs */ I can no longer attend.</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 30 May, 2023 at the University of Ottawa, prior to pgCon 2023. In order to keep the numbers manageable, this meeting is by '''invitation only'''.<br />
Any questions regarding the invitations to this event should be directed to the team of individuals tasked with coming up with the list of people to invite:<br />
<br />
* Andres Freund<br />
* Stephen Frost<br />
* Dave Page<br />
<br />
An Unconference will be held on Friday for in-depth discussion of technical topics.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Define the schedule for the upcoming releases<br />
* Address any proposed timing, policy, or procedure issues<br />
* Receive updates from project sub-teams on their activities and discuss any resulting issues or concerns.<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
<br />
== Time & Location ==<br />
<br />
The meeting will (probably) be:<br />
<br />
* 9:00AM to 12PM<br />
* DMS 3105 - Desmarais Hall, 55 Laurier Avenue East<br />
* University of Ottawa.<br />
<br />
Lunch will be served during the meeting.<br />
<br />
== COVID-19 ==<br />
<br />
The University of Ottawa's COVID-19 guidance can be found at https://www.uottawa.ca/en/covid-19. Wearing of masks at the Developer Meeting will be optional, however we do ask that people do not attend if they have COVID symptoms or have tested positive.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname). Note that we can accommodate a '''maximum of 30'''!<br />
<br />
# Nathan Bossart<br />
# Joe Conway<br />
# Jeff Davis<br />
# Mark Dilger<br />
# Peter Eisentraut<br />
# Andres Freund<br />
# Stephen Frost<br />
# Etsuro Fujita<br />
# Peter Geoghegan<br />
# Magnus Hagander<br />
# Amit Kapila<br />
# Jonathan Katz<br />
# Tom Lane<br />
# Heikki Linnakangas<br />
# Noah Misch<br />
# Thomas Munro<br />
# Dave Page<br />
# Michael Paquier<br />
# Melanie Plageman<br />
# Masahiko Sawada<br />
# Tomas Vondra<br />
<br />
The following people will not be in Ottawa, and do not plan to attend:<br />
<br />
# Masao Fujii<br />
# Daniel Gustafsson<br />
# Álvaro Herrera<br />
# Tatsuo Ishii<br />
# Alexander Korotkov<br />
# Amit Langote<br />
# Dean Rasheed<br />
# David Rowley<br />
<br />
== Agenda Items ==<br />
<br />
* 16.0 release and commitfest schedule (Dave)<br />
* Renaming "master" branch to "main"? (Michael)<br />
* A brief PG15 RMT postmortem and what can we improve? (Jonathan)<br />
* What are the big challenges for our users? What are the big challenges for us to solve? (Jonathan)<br />
* (Possible topic on releases) (Jonathan)<br />
* Cloud operators have data of value to this community, e.g. frequency of errors that should never happen. What sort of data sharing regime might provide a good balance between value to the community and comfort for cloud operators? (Noah)<br />
* ''Please add suggestions for agenda items here. (with your name)''<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave Page<br />
<br />
|- <br />
|09:10 - 09:20<br />
|Release and commitfest schedules<br />
|Dave Page<br />
<br />
|- <br />
|??:?? - ??:??<br />
|TBD<br />
|TBD<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- <br />
|??:?? - ??:??<br />
|TBD<br />
|TBD<br />
<br />
|- <br />
|11:50 - 12:00<br />
|Any other business<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:00<br />
|Lunch<br />
|<br />
<br />
|}<br />
<br />
Note: This timetable is a rough guide only. Items will start as soon as the previous discussion is complete (breaks will not move materially however). Any remaining time before lunch may be used for Commitfest item triage or other activities.<br />
<br />
[[Category:Developer Meeting]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_16_Open_Items&diff=37738PostgreSQL 16 Open Items2023-04-12T09:11:25Z<p>Davidrowley: /* Older bugs affecting stable branches */ add bug 17862</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
'''NOTE''': If known, please list the Owner of the open item.<br />
<br />
* Revert {{PgCommitURL|ec386948948c1708c0c28c48ef08b9c4dd9d47cc}}<br />
** {{messageLink|20230330105325.y6uvpalspynf2frt@alvherre.pgsql|Re: "variable not found in subplan target list"}}<br />
* Is it OK that WL_SOCKET_ACCEPT is less fair on Windows than on Unix (and than the coding before 16) when there are multiple server sockets configured?<br />
** {{messageLink|CA%2BhUKG%2BA2dk29hr5zRP3HVJQ-_PncNJM6HVQ7aaYLXLRBZU-xw%40mail.gmail.com|WL_SOCKET_ACCEPT fairness on Windows}} has a (blind) patch to fix that, but would need a Windows hacker to test<br />
* Planner makes improper clause pushdown decisions due to outer-join-aware-Vars changes<br />
** {{messageLink|0b819232-4b50-f245-1c7d-c8c61bf41827@postgrespro.ru|Clause accidentally pushed down}}<br />
** {{messageLink|CAHewXNks3w_Vy9CWoVtHx1XSaeiFpsOzh-zy5eu0Khp1PtG1sA@mail.gmail.com|wrong results due to qual pushdown}}<br />
** Owner: Tom Lane (2489d76c4)<br />
* Switch to ICU for 17?<br />
** {{messageLink|82c4c816-06f6-d3e3-ba02-fca4a5cef065@enterprisedb.com|I suggest waiting until next week to commit it and then see what happens}}<br />
** [https://commitfest.postgresql.org/42/4169/ CF Entry]<br />
* {{messageLink|3590249.1680971629@sss.pgh.pa.us|Assertion failure with parallel full hash join}}<br />
* {{messageLink|CAD21AoBS7o6Ljt_vfqPQPf67AhzKu3fR0iqk8B%3DvVYczMugKMQ%40mail.gmail.com|VacuumUpdateCosts() logging condition incorrect for some initial values of vacuum_cost_delay}}<br />
* {{messageLink|ZDDO6jaESKaBgej0@tamriel.snowman.net|De-revert "Add support for Kerberos credential delegation"}}<br />
** Owner: Stephen Frost<br />
** Original commit: {{PgCommitURL|3d4fa227bce4294ce1cc214b4a9d3b7caa3f0454}}<br />
** Revert: ({{PgCommitURL|3d03b24c350ab060bb223623bdff38835bd7afd0}}<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/268fd337-8bb7-92e6-0da2-416c022c11f3%40enterprisedb.com Reconsider a utility_query_id GUC to control if query jumbling of utilities can go through the past string-only mode and the new mode?]<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer] [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report] [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report] [https://www.postgresql.org/message-id/flat/CAPH-tTxLf44s3CvUUtQpkDr1D8Hxqc2NGDzGXS1ODsfiJ6WSqA%40mail.gmail.com Another report] [https://www.postgresql.org/message-id/flat/a53cacb0-8835-57d6-31e4-4c5ef196de1a@deepbluecap.com Another report]<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/ZArVOMifjzE7f8W7%40paquier.xyz Requiring recovery.signal or standby.signal when recovering with a backup_label]<br />
** This is a rather old behavior that affects all stable branches, still not something that should be backpatched as-is.<br />
<br />
* {{messageLink|cfcca574-6967-c5ab-7dc3-2c82b6723b99@mail.ru|pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum}}<br />
** {{messageLink|1649062270.289865713@f403.i.mail.ru|Thread with patch}} [https://commitfest.postgresql.org/43/3739/ CF Entry]<br />
<br />
* {{messageLink|CAAKRu_bETD%2BAri600h6fRjX2p8rJSeMAUp%3D_y88juqOZgouTSg%40mail.gmail.com|Can't disable autovacuum cost delay through storage parameter}}<br />
<br />
* {{messageLink|17862-1ab8f74b0f7b0611@postgresql.org|WindowAgg startup costs don't take into account partition bound. Can lead to incorrect use of cheap startup plans}}<br />
** {{messageLink|CAApHDvrB0S5BMv+0-wTTqWFE-BJ0noWqTnDu9QQfjZ2VSpLv_g@mail.gmail.com|Patch to fix and discussion}}<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
** Fixed at: {{PgCommitURL|8fcb32db98eda1ad2a0c0b40b1cbb5d9a7aa68f0}} and {{PgCommitURL|ffd1b6bb6f8a2ffc929699772610c6925364dbb3}} for HEAD.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAC+AXB26a4EmxM2suXxPpJaGrqAdxracd7hskLg-zxtPB50h7A@mail.gmail.com Fix fseek() detection of unseekable files on WIN32]<br />
** Fixed at: {{PgCommitURL|a923e21631a29dc8b8781d7d02b5003d0df64ca3}} and {{PgCommitURL|765f5df726918bcdcfd16bcc5418e48663d1dd59}}, down to 14.<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 16beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAEZATCWETioXs5kY8vT6BVguY41_wD962VDk%3Du_Nvd7S1UXzuQ%40mail.gmail.com ERROR: ORDER/GROUP BY expression not found in targetlist]<br />
** Fixed at: {{PgCommitURL|da5800d5fa636c6e10c9c98402d872c76aa1c8d0}}<br />
<br />
* [https://www.postgresql.org/message-id/20230212233711.GA1316@telsasoft.com various elogs hit by sqlsmith (ExecRTCheckPerms() and many prunable partitions)]<br />
** Fixed at: {{PgCommitURL|c7468c73f7b6e842a53c12eaee5578a76a8fa7a6}}<br />
<br />
* [https://www.postgresql.org/message-id/20230228235834.GC30529@telsasoft.com pg_dump: zlib compression fails for empty objects (LOs)]<br />
** Fixed at: {{PgCommitURL|00d9dcf5bebbb355152a60f0e2120cdf7f9e7ddd}}<br />
<br />
* [https://www.postgresql.org/message-id/20230227044910.GO1653@telsasoft.com pg_dump: lz4 compression uses no persistent state and writes a block header for every row]<br />
** Fixed at: {{PgCommitURL|0070b66fef21e909adb283f7faa7b1978836ad75}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Beta 1: TBD<br />
* Feature Freeze: April 8, 2023 0:00 AoE ('''Last Day to Commit Features''')<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
* [[PostgreSQL 15 Open Items]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PgCon_2023_Developer_Meeting&diff=37697PgCon 2023 Developer Meeting2023-03-28T19:20:05Z<p>Davidrowley: /* RSVPs */ Added self. Corrected alphabetical order by surname</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 30 May, 2023 at the University of Ottawa, prior to pgCon 2023. In order to keep the numbers manageable, this meeting is by '''invitation only'''.<br />
Any questions regarding the invitations to this event should be directed to the team of individuals tasked with coming up with the list of people to invite:<br />
<br />
* Andres Freund<br />
* Stephen Frost<br />
* Dave Page<br />
<br />
An Unconference will be held on Friday for in-depth discussion of technical topics.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Define the schedule for the upcoming releases<br />
* Address any proposed timing, policy, or procedure issues<br />
* Receive updates from project sub-teams on their activities and discuss any resulting issues or concerns.<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
<br />
== Time & Location ==<br />
<br />
The meeting will (probably) be:<br />
<br />
* 9:00AM to 12PM<br />
* DMS 3105 - Desmarais Hall, 55 Laurier Avenue East<br />
* University of Ottawa.<br />
<br />
Lunch will be served during the meeting.<br />
<br />
== COVID-19 ==<br />
<br />
The University of Ottawa's COVID-19 guidance can be found at https://www.uottawa.ca/en/covid-19. Wearing of masks at the Developer Meeting will be optional, however we do ask that people do not attend if they have COVID symptoms or have tested positive.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname). Note that we can accommodate a '''maximum of 30'''!<br />
<br />
# Joe Conway<br />
# Jeff Davis<br />
# Peter Eisentraut<br />
# Andres Freund<br />
# Stephen Frost<br />
# Etsuro Fujita<br />
# Magnus Hagander<br />
# Jonathan Katz<br />
# Alexander Korotkov<br />
# Tom Lane<br />
# Heikki Linnakangas<br />
# Noah Misch<br />
# Thomas Munro<br />
# Dave Page<br />
# Michael Paquier<br />
# Melanie Plageman<br />
# David Rowley<br />
<br />
The following people will not be in Ottawa, and do not plan to attend:<br />
<br />
# Daniel Gustafsson<br />
# Tatsuo Ishii<br />
# Dean Rasheed<br />
<br />
== Agenda Items ==<br />
<br />
* 16.0 release and commitfest schedule (Dave)<br />
* ''Please add suggestions for agenda items here. (with your name)''<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave Page<br />
<br />
|- <br />
|09:10 - 09:20<br />
|Release and commitfest schedules<br />
|Dave Page<br />
<br />
|- <br />
|??:?? - ??:??<br />
|TBD<br />
|TBD<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- <br />
|??:?? - ??:??<br />
|TBD<br />
|TBD<br />
<br />
|- <br />
|11:50 - 12:00<br />
|Any other business<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:00<br />
|Lunch<br />
|<br />
<br />
|}<br />
<br />
Note: This timetable is a rough guide only. Items will start as soon as the previous discussion is complete (breaks will not move materially however). Any remaining time before lunch may be used for Commitfest item triage or other activities.<br />
<br />
[[Category:Developer Meeting]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=Todo&diff=37540Todo2023-02-09T01:47:38Z<p>Davidrowley: /* Functions */ Add link to explain that boyer-moore for LIKE might be hard</p>
<hr />
<div><div style="margin: 1ex 1em; float: right;"><br />
__TOC__<br />
</div><br />
<br />
This list contains some known PostgreSQL bugs, some feature requests, and some things we are not even sure we want. Many of these items are hard, and some are perhaps impossible. If you would like to work on an item, please read the [[Developer FAQ]] first. There is also a [[Development_information|development information page]].<br />
<br />
* {{TodoPending}} - marks incomplete items<br />
* {{TodoDone}} - marks changes that are done, and will appear in the PostgreSQL 16 release.<br />
<br />
Over time, it may become clear that a TODO item has become outdated or otherwise determined to be either too controversial or not worth the development effort. Such items should be retired to the [[Not Worth Doing]] page.<br />
<br />
For help on editing this list, please see [[Talk:Todo]]. <b>Please do not add or remove items here without discussion on the [[Mailing_Lists|mailing list]].</b><br />
<br />
== Development Process ==<br />
<br />
<b>WARNING for Developers:</b> Unfortunately this list does not contain all the information necessary for someone to start coding a feature. Some of these items might have become unnecessary since they were added --- others might be desirable but the implementation might be unclear. When selecting items listed below, be prepared to first discuss the value of the feature. '''Do not assume that you can select one, code it and then expect it to be committed.''' Always discuss design on Hackers list before starting to code. The flow should be:<br />
<br />
Desirability -> Design -> Implement -> Test -> Review -> Commit<br />
<br />
== Administration ==<br />
<br />
{{TodoItem<br />
|Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptly<br />
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php <nowiki>Removing unreferenced files</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow log_min_messages to be specified on a per-module basis<br />
|This would allow administrators to see more detailed information from specific sections of the backend, e.g. checkpoints, autovacuum, etc. Another idea is to allow separate configuration files for each module, or allow arbitrary SET commands to be passed to them. See also [[Logging Brainstorm]].}}<br />
<br />
{{TodoItem<br />
|Prevent query cancel packets from being replayed by an attacker, especially when using SSL<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php <nowiki>Replay attack of query cancel</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider supporting incremental base backups<br />
* http://www.postgresql.org/message-id/543D5AA7.9@2ndquadrant.it<br />
}}<br />
<br />
=== Configuration files ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItemDone<br />
|Allow pg_hba.conf to process include files<br />
* [http://www.postgresql.org/message-id/86fvnm5t44.fsf@jerry.enova.com HBA files w/include support]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block<br />
* Currently it displays zero.<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Tablespaces ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow a database in tablespace t1 with tables created in tablespace t2 to be used as a template for a new database created with default tablespace t2<br />
|Currently all objects in the default database tablespace must have default tablespace specifications. This is because new databases are created by copying directories. If you mix default tablespace tables and tablespace-specified tables in the same directory, creating a new database from such a mixed directory would create a new database with tables that had incorrect explicit tablespaces. To fix this would require modifying pg_class in the newly copied database, which we don't currently do.}}<br />
<br />
{{TodoItem<br />
|Allow reporting of which objects are in which tablespaces<br />
|This item is difficult because a tablespace can contain objects from multiple databases. There is a server-side function that returns the databases which use a specific tablespace, so this requires a tool that will call that function and connect to each database to find the objects in each database for that tablespace.}}<br />
<br />
{{TodoItem<br />
|Allow WAL replay of CREATE TABLESPACE to work when the directory structure on the recovery computer is different from the original<br />
* [https://www.postgresql.org/message-id/flat/CALfoeisEF92F5nJ-aAcuWTvF_Aogxq_1bHLem_kVfM_tHc2mfg%40mail.gmail.com Some possible approaches]<br />
* [https://www.postgresql.org/message-id/20180214042443.GB1993%40paquier.xyz Remarks about the difficulty of the item]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow tablespaces on RAM-based partitions for unlogged tables<br />
* http://archives.postgresql.org/pgsql-advocacy/2011-05/msg00033.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow toast tables to be moved to a different tablespace<br />
* [http://archives.postgresql.org/pgsql-hackers/2011-05/msg00980.php moving toast table to its own tablespace]<br />
* {{messageLink|CAFEQCbH756DyyAPQ1ykh3+b+kE1-EhWRww1WO_x5v38C-uLnUg@mail.gmail.com|patch : Allow toast tables to be moved to a different tablespace}}<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Statistics Collector ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Testing pgstat via pg_regress is tricky and inefficient. Consider making a dedicated pgstat test-suite.<br />
* [http://www.postgresql.org/message-id/20141216142937.GX1768@alvh.no-ip.org <nowiki>Re: REVIEW: Track TRUNCATE via pgstat</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Teach stats collector to differentiate between internal and leaf index pages<br />
* [https://www.postgresql.org/message-id/flat/CAH2-WzmdZqxCS1widYzjDAM%2BZ-Jz%3DejJoaWXDVw9Qy1UsK0tLA%40mail.gmail.com <nowiki>Stats collector's idx_blks_hit value is highly misleading in practice</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== SSL ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
| Allow automatic selection of SSL client certificates from a certificate store<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg00406.php <nowiki>Allow multiple certificates or keys in the postgresql.crt/.key files</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Standby server mode ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
| Prevent variables inherited from the server environment from being used for making streaming replication connections<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg01011.php <nowiki>Re: Parameter name standby_mode</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Data Types ==<br />
<br />
{{TodoItem<br />
|Add support for public SYNONYMs<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php <nowiki>Proposal for SYNONYMS</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php<br />
* http://archives.postgresql.org/pgsql-general/2010-12/msg00139.php<br />
}}<br />
<br />
{{TodoItem<br />
|Consider a special data type for regular expressions<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php <nowiki>Why is there a tsquery data type?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow deleting enumerated values from an existing enumerated data type<br />
* [http://www.postgresql.org/message-id/CAO%3D2mx6uvgPaPDf-rHqG8%3D1MZnGyVDMQeh8zS4euRyyg4D35OQ@mail.gmail.com Alter or rename enum value]<br />
}}<br />
<br />
{{TodoItem<br />
|Add overlaps geometric operators that ignore point overlaps<br />
* http://archives.postgresql.org/pgsql-hackers/2010-03/msg00861.php<br />
}}<br />
<br />
=== Dates and Times ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow infinite intervals just like infinite timestamps<br />
* https://www.postgresql.org/message-id/4EB095C8.1050703@agliodbs.com<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Arrays ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow single-byte header storage for array elements}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Text Search ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Consider changing error to warning for strings larger than one megabyte<br />
* [http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php <nowiki>BUG #3975: tsearch2 index should not bomb out of 1Mb limit</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve default parser, to more easily allow adding new tokens<br />
* http://archives.postgresql.org/message-id/23485.1297727826@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
|Add additional support functions<br />
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg00319.php<br />
}}<br />
<br />
=== XML ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add XML Schema validation and xmlvalidate functions (SQL:2008)}}<br />
<br />
{{TodoItem<br />
|Add xmlvalidatedtd variant to support validating against a DTD?}}<br />
<br />
{{TodoItem<br />
|Relax-NG validation; libxml2 supports this already}}<br />
<br />
{{TodoItem<br />
|Add functions from SQL:2006: XMLDOCUMENT, XMLCAST, XMLTEXT}}<br />
<br />
{{TodoItem<br />
|Add XMLNAMESPACES support in XMLELEMENT and elsewhere}}<br />
<br />
{{TodoItem<br />
|Report errors returned by the XSLT library<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg00562.php<br />
}}<br />
<br />
{{TodoItem<br />
|XML Canonical: Convert XML documents to canonical form to compare them. libxml2 has support for this.}}<br />
<br />
{{TodoItem<br />
|Add pretty-printed XML output option<br />
|Parse a document and serialize it back in some indented form. libxml2 might support this.}}<br />
<br />
{{TodoItem<br />
|Add XMLQUERY (from the SQL/XML standard)}}<br />
<br />
{{TodoItem<br />
|Allow XML shredding<br />
|In some cases shredding could be better option (if there is no need to keep XML docs entirely, e.g. if we have already developed tools that understand only relational data. This would be a separate module that implements annotated schema decomposition technique, similar to DB2 and SQL Server functionality.}}<br />
<br />
{{TodoItem<br />
|XPath: Adding the <x> at the root causes problems [http://archives.postgresql.org/pgsql-bugs/2008-05/msg00184.php] [http://archives.postgresql.org/pgsql-bugs/2008-07/msg00054.php] [http://archives.postgresql.org/pgsql-general/2008-07/msg00613.php]}}<br />
<br />
{{TodoItem<br />
|Verify Xpath escaping behavior<br />
* [http://www.postgresql.org/message-id/E1VOXZv-0008Q9-0Z@wrigleys.postgresql.org Xpath behaviour unintuitive / arguably wrong]<br />
* [http://www.postgresql.org/message-id/CAAY5AM1L83y79rtOZAUJioREO6n4%3DXAFKcGu6qO3hCZE1yJytg@mail.gmail.com xpath missing entity decoding - bug or feature]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Functions ==<br />
<br />
{{TodoItem<br />
|Implement Boyer-Moore searching in LIKE queries<br />
* {{messageLink|27645.1220635769@sss.pgh.pa.us|TODO item: Implement Boyer-Moore searching (First time hacker)}}<br />
* [https://www.postgresql.org/message-id/CALkFZpcbipVJO%3DxVvNQMZ7uLUgHzBn65GdjtBHdeb47QV4XzLw@mail.gmail.com Implement Boyer-Moore searching in LIKE queries]<br />
* [https://www.postgresql.org/message-id/CAPfd9M%3DkwDT2TRTRNFUcOkoFLa5FL2Dxshjqz3zBrbqQ%3D1agLA@mail.gmail.com Details of why this might be hard]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent malicious functions from being executed with the permissions of unsuspecting users<br />
|Indexed functions are safe, so VACUUM and ANALYZE are safe too. Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable. <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php <nowiki>Some notes about the index-functions security vulnerability</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix /contrib/btree_gist's implementation of inet indexing<br />
* [http://archives.postgresql.org/pgsql-bugs/2010-10/msg00099.php <nowiki>BUG #5705: btree_gist: Index on inet changes query result</nowiki>]<br />
}}<br />
<br />
== Multi-Language Support ==<br />
<br />
{{TodoItem<br />
|Add NCHAR (as distinguished from ordinary varchar)<br />
* [http://www.postgresql.org/message-id/A756FAD7EDC2E24F8CAB7E2F3B5375E918B12BC0@FALEX03.au.fjanz.com UTF8 national character data type support WIP patch and list of open issues.]<br />
}}<br />
<br />
{{TodoItem<br />
|Integrate collations with text search configurations<br />
* [http://archives.postgresql.org/message-id/28887.1303579034@sss.pgh.pa.us <nowiki>Some TODO items for collations</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Integrate collations with to_char() and related functions<br />
* [http://archives.postgresql.org/message-id/28887.1303579034@sss.pgh.pa.us <nowiki>Some TODO items for collations</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Support collation-sensitive equality and hashing functions<br />
* [http://archives.postgresql.org/pgsql-hackers/2011-06/msg00472.php <nowiki> contrib/citext versus collations</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Support multiple simultaneous character sets, per SQL:2008}}<br />
<br />
{{TodoItem<br />
|Improve UTF8 combined character handling?}}<br />
<br />
{{TodoItem<br />
|Fix contrib/fuzzystrmatch to work with multibyte encodings<br />
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00047.php <nowiki> soundex function returns UTF-16 characters</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg00138.php <nowiki> dmetaphone woes</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Change memory allocation for multi-byte functions so memory is allocated inside conversion functions<br />
|Currently we preallocate memory based on worst-case usage.}}<br />
<br />
{{TodoItem<br />
|Add ability to use case-insensitive regular expressions on multi-byte characters<br />
|Currently it works for UTF-8, but not other multi-byte encodings<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg00433.php <nowiki>Regexps vs. locale</nowiki>]<br />
* {{MessageLink|20091201210024.B1393753FB7@cvs.postgresql.org|A partial solution for UTF-8}}<br />
}}<br />
<br />
{{TodoItem<br />
|Improve encoding of connection startup messages sent to the client<br />
|Currently some authentication error messages are sent in the server encoding<br />
* [http://archives.postgresql.org/pgsql-general/2008-12/msg00801.php <nowiki>encoding of PostgreSQL messages</nowiki>]<br />
* [http://www.postgresql.org/message-id/20131220030725.GA1411150@tornado.leadboat.com multibyte messages are displayed incorrectly on the client]<br />
}}<br />
<br />
{{TodoItem<br />
|Windows: Cache MessageEncoding conversion for use outside transactions<br />
* http://www.postgresql.org/message-id/20150812055719.GA1945333@tornado.leadboat.com<br />
}}<br />
<br />
== Views and Rules ==<br />
<br />
{{TodoItem<br />
|Improve ability to modify views via ALTER TABLE<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00691.php <nowiki>Re: idea: storing view source in system catalogs</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg01410.php <nowiki>modifying views</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00300.php <nowiki>Re: patch: Add columns via CREATE OR REPLACE VIEW</nowiki>]<br />
}}<br />
<br />
== SQL Commands ==<br />
<br />
{{TodoItem<br />
|Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT<br />
* [https://www.postgresql.org/message-id/flat/CAJZSWkWN3YwQ01C3%2Bcq0%2BeyZ1DmK%3D69_6vryrsVGMC%3D%2BfWrSZA%40mail.gmail.com/ Adding CORRESPONDING to Set Operations.]<br />
* [http://web.archive.org/web/20161019182747/dissipatedheat.com/2011/11/10/how-not-to-write-a-patch-for-postgresql/ How not to write this patch.]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve type determination of unknown (NULL or quoted literal) result columns for UNION/INTERSECT/EXCEPT<br />
* [http://archives.postgresql.org/message-id/9799.1302719551@sss.pgh.pa.us <nowiki>UNION construct type cast gives poor error message</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow prepared transactions with temporary tables created and dropped in the same transaction, and when an ON COMMIT DELETE ROWS temporary table is accessed<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php <nowiki>Re: &quot;could not open relation 1663/16384/16584: No such file or directory&quot; in a specific combination of transactions with temp tables</nowiki>]<br />
* [http://archives.postgresql.org/message-id/492543D5.9050904@enterprisedb.com A suggestion on how to implement this]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow NOTIFY in rules involving conditionals}}<br />
<br />
{{TodoItem<br />
|Allow LISTEN on patterns<br />
* http://www.postgresql.org/message-id/52693FC5.7070507@gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Simplify dropping roles that have objects in several databases}}<br />
<br />
{{TodoItem<br />
|Add support for WITH RECURSIVE ... CYCLE<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00291.php <nowiki>WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows</nowiki>]}}<br />
<br />
{{TodoItem<br />
|Add DEFAULT .. AS OWNER so permission checks are done as the table owner<br />
|This would be useful for SERIAL nextval() calls and CHECK constraints.}}<br />
<br />
{{TodoItem<br />
|Add comments on system tables/columns using the information in catalogs.sgml<br />
|Ideally the information would be pulled from the SGML file automatically.}}<br />
<br />
{{TodoItem<br />
|Prevent the specification of conflicting transaction read/write options<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-01/msg00684.php <nowiki>Re: SET TRANSACTION and SQL Standard</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow PREPARE of cursors}}<br />
<br />
{{TodoItem<br />
|Have DISCARD PLANS discard plans cached by functions<br />
|DISCARD ALL should do the same.<br />
* http://archives.postgresql.org/pgsql-hackers/2011-01/msg00431.php<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid multiple-evaluation of BETWEEN and IN arguments containing volatile expressions<br />
* http://archives.postgresql.org/message-id/4D95B605.2020709@enterprisedb.com<br />
}}<br />
<br />
=== CREATE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow CREATE TABLE AS to determine column lengths for complex expressions like SELECT col1 || col2}}<br />
<br />
{{TodoItem<br />
|Have WITH CONSTRAINTS also create constraint indexes<br />
* [http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php <nowiki>Re: CREATE TABLE LIKE INCLUDING INDEXES support</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Move NOT NULL constraint information to pg_constraint<br />
|Currently NOT NULL constraints are stored in pg_attribute without any designation of their origins, e.g. primary keys. One manifest problem is that dropping a PRIMARY KEY constraint does not remove the NOT NULL constraint designation. Another issue is that we should probably force NOT NULL to be propagated from parent tables to children, just as CHECK constraints are. (But then does dropping PRIMARY KEY affect children?)<br />
* http://archives.postgresql.org/message-id/19768.1238680878@sss.pgh.pa.us<br />
* http://archives.postgresql.org/message-id/200909181005.n8IA5Ris061239@wwwmaster.postgresql.org<br />
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg01223.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg00358.php<br />
* [https://www.postgresql.org/message-id/CAB7nPqTPXgX9HiyhhtAgpW7jbA1iskMCSoqXPEEB_KYXYy1E1Q@mail.gmail.com Prevent ALTER TABLE DROP NOT NULL on child tables if parent column has it]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent concurrent CREATE TABLE from sometimes returning a cryptic error message<br />
* [http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php <nowiki>BUG #3692: Conflicting create table statements throw unexpected error</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add CREATE SCHEMA ... LIKE that copies a schema}}<br />
<br />
{{TodoItem<br />
|Fix CREATE OR REPLACE FUNCTION to not leave objects depending on the function in inconsistent state<br />
* [http://archives.postgresql.org/pgsql-general/2008-08/msg00985.php indexes on functions and create or replace function]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow temporary tables to exist as empty by default in all sessions<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php <nowiki>what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg01329.php <nowiki>idea: global temp tables</nowiki>]<br />
* [http://archives.postgresql.org//pgsql-hackers/2009-05/msg00016.php <nowiki>Re: idea: global temp tables</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg01098.php <nowiki>global temporary tables</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2012-04/msg01148.php Temporary tables under hot standby]<br />
* [http://www.postgresql.org/message-id/CAFj8pRC2h6qhHsFbcE7b_7SagiS6o%3D5J2UvCwCb05Ka1XFv_Ng@mail.gmail.com Implementation of global temporary tables?]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow the creation of "distinct" types<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01647.php <nowiki>Distinct types</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider analyzing temporary tables when they are first used in a query<br />
|Autovacuum cannot analyze or vacuum temporary tables.<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg00416.php <nowiki>autovacuum and temp tables support</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== UPDATE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Research self-referential UPDATEs that see inconsistent row versions in read-committed mode<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php <nowiki>Concurrently updating an updatable view</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve performance of EvalPlanQual mechanism that rechecks already-updated rows<br />
|This is related to the previous item, which questions whether it even has the right semantics<br />
* [http://archives.postgresql.org/pgsql-bugs/2008-09/msg00045.php <nowiki>BUG #4401: concurrent updates to a table blocks one update indefinitely</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-bugs/2009-07/msg00302.php <nowiki>BUG #4945: Parallel update(s) gone wild</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== ALTER ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Have ALTER TABLE RENAME of a SERIAL column rename the sequence<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php <nowiki>Re: newbie: renaming sequences task</nowiki>]<br />
* [http://archives.postgresql.org/message-id/CADLWmXUV4LbLhMZL8rYMhCy72aZZLB5BSARPQVgoX0BrxA0FFg@mail.gmail.com renaming implicit sequences]<br />
}}<br />
<br />
{{TodoItem<br />
|Add ALTER DOMAIN to modify the underlying data type}}<br />
<br />
{{TodoItem<br />
|Allow ALTER TABLESPACE to move the tablespace to different directories}}<br />
<br />
{{TodoItem<br />
|Allow moving system tables to other tablespaces, where possible<br />
|Currently non-global system tables must be in the default database tablespace. Global system tables can never be moved.}}<br />
<br />
{{TodoItem<br />
|Have ALTER INDEX update the name of a constraint using that index}}<br />
<br />
{{TodoItem<br />
|Allow column display reordering by recording a display, storage, and permanent id for every column?<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php <nowiki>Re: column ordering, was Re: [PATCHES] Enums patch v2</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg01029.php <nowiki>Column reordering in pg_dump</nowiki>]<br />
* http://archives.postgresql.org/message-id/1324412114-sup-9608@alvh.no-ip.org<br />
* [http://www.postgresql.org/message-id/CAApHDvqhnuznxd4xVMFDcGn+nHVYyUtJ-TvbRsOuR%3DPaVbbGqw@mail.gmail.com logical column order and physical column order]<br />
* [http://www.postgresql.org/message-id/20141209174146.GP1768@alvh.no-ip.org logical column ordering]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow deactivating (and reactivating) indexes via ALTER TABLE<br />
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg01191.php<br />
}}<br />
<br />
{{TodoItem<br />
|Add ALTER OPERATOR ... RENAME<br />
|needs to consider effects of changing operator precedence<br />
* [http://archives.postgresql.org/message-id/1322948781.26266.9.camel@vanquo.pezone.net Missing rename support]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== CLUSTER ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Automatically maintain clustering on a table<br />
|This might require some background daemon to maintain clustering during periods of low usage. It might also require tables to be only partially filled for easier reorganization. Another idea would be to create a merged heap/index data file so an index lookup would automatically access the heap data too. A third idea would be to store heap rows in hashed groups, perhaps using a user-supplied hash function.<br />
* [http://archives.postgresql.org/pgsql-performance/2004-08/msg00350.php <nowiki>Equivalent praxis to CLUSTERED INDEX?</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00155.php <nowiki>Re: Grouped Index Tuples</nowiki>]<br />
* http://community.enterprisedb.com/git/<br />
* [http://archives.postgresql.org/pgsql-performance/2009-10/msg00346.php <nowiki>Re: maintain_cluster_order_v5.patch</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
| Allow CLUSTER to be used on partial indexes<br />
* http://www.postgresql.org/message-id/CAMkU%3D1zYwoHHsqJ8wfK3GdG_t_a6t4RK-GFDSKymQ0EGP%3DtypA@mail.gmail.com<br />
}} <br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== COPY ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow COPY to report error lines and continue<br />
|This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure. <br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php <nowiki>Re: VLDB Features</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow COPY to report errors sooner<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php <nowiki>Timely reporting of COPY errors</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow COPY FROM to create index entries in bulk<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php <nowiki>Batch update of indexes on data loading</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve COPY performance<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php <nowiki>Re: 8.3 / 8.2.6 restore comparison</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01882.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow a stalled COPY to exit if the backend is terminated<br />
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00067.php <nowiki>Re: possible bug not in open items</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow COPY "text" format to output a header<br />
* [http://www.postgresql.org/message-id/CACfv+pJ31tesLvncJyP24quo8AE+M0GP6p6MEpwPv6yV8%3DsVHQ@mail.gmail.com Why doesn't COPY support the HEADER options for tab-separated output?]<br />
}}<br />
<br />
{{TodoItem<br />
|Have COPY FREEZE set PD_ALL_VISIBLE<br />
* [http://www.postgresql.org/message-id/CAMkU%3D1w3osJJ2FneELhhNRLxfZitDgp9FPHee08NT2FQFmz_pQ@mail.gmail.com items]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== GRANT/REVOKE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow dropping of a role that has connection rights<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00736.php <nowiki>DROP ROLE dependency tracking ...</nowiki>]<br />
}}<br />
{{TodoEndSubsection}}<br />
<br />
=== DECLARE CURSOR ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Prevent DROP TABLE from dropping a table referenced by its own open cursor?}}<br />
<br />
{{TodoItem<br />
|Provide some guarantees about the behavior of cursors that invoke volatile functions<br />
* [http://archives.postgresql.org/message-id/20997.1244563664@sss.pgh.pa.us Re: Cursor with hold emits the same row more than once across commits in 8.3.7]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== SHOW/SET ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM ANALYZE, and CLUSTER}}<br />
<br />
{{TodoItem<br />
|Rationalize the discrepancy between settings that use values in bytes and SHOW that returns the object count<br />
* [http://archives.postgresql.org/pgsql-docs/2008-07/msg00007.php <nowiki>Re: [ADMIN] shared_buffers and shmmax</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== ANALYZE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Improve how ANALYZE computes in-doubt tuples<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php <nowiki>VACUUM/ANALYZE counting of in-doubt tuples</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Remove quadratic time in statistics sender when analyzing many tables<br />
* [http://www.postgresql.org/message-id/flat/CAMkU%3D1wLjAsmJNuB6ZObZmGHqi9jLbK6n1eSgnOc5J1-AUsvUA@mail.gmail.com Thousands of schemas and ANALYZE goes out of memory]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce memory use when analyzing many tables in a single command by making catcache and syscache flushable or bounded.<br />
* [http://www.postgresql.org/message-id/flat/CAMkU%3D1yZnAYvMHENt8%3D9pgwE8q5zmX+mG%3DSXbFHiLkq_qn0B7Q@mail.gmail.com Thousands of schemas and ANALYZE goes out of memory]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== EXPLAIN ===<br />
{{TodoSubsection}}<br />
{{TodoItem<br />
|Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and actual row counts differ by a specified percentage}}<br />
<br />
{{TodoItem<br />
|Have EXPLAIN ANALYZE report rows as floating-point numbers<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg01363.php <nowiki>explain analyze rows=%.0f</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00108.php <nowiki>Re: explain analyze rows=%.0f</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Have EXPLAIN ANALYZE report buckets and memory usage for HashAggregate<br />
* [https://www.postgresql.org/message-id/flat/2527f5cb-5992-ae66-f3ec-4aa2396065ec%402ndquadrant.com <nowiki>to-do item for explain analyze of hash aggregates? </nowiki>]<br />
}}<br />
<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Window Functions ===<br />
See {{messageLink|357.1230492361@sss.pgh.pa.us|TODO items for window functions}}.<br />
{{TodoSubsection}}<br />
{{TodoItem<br />
|Support creation of user-defined window functions<br />
|We have the ability to create new window functions written in C. Is it<br />
worth the effort to create an API that would let them be written in PL/pgsql, etc?}}<br />
<br />
{{TodoItem<br />
|Investigate tuplestore performance issues<br />
|The tuplestore_in_memory() thing is just a band-aid, we ought to try to solve it properly. tuplestore_advance seems like a weak spot as well.<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg00152.php <nowiki>tuplestore potential performance problem</nowiki>]<br />
}}<br />
<br />
{{TodoItem|Do we really need so much duplicated code between Agg and WindowAgg?}}<br />
<br />
{{TodoItem<br />
|Teach planner to evaluate multiple windows in the optimal order<br />
|Currently windows are always evaluated in the query-specified order.<br />
* http://archives.postgresql.org/message-id/3CDAD71E9D70417290FCF66F0178D1E1@amd64<br />
}}<br />
<br />
{{TodoItem<br />
|Implement DISTINCT clause in window aggregates<br />
|Some proprietary RDBMSs have implemented it already, so it helps with porting from those.}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Integrity Constraints ==<br />
=== Keys ===<br />
<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Improve deferrable unique constraints for cases with many conflicts<br />
|The current implementation fires a trigger for each potentially conflicting row. This might not scale well for an update that changes many key values at once.<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Referential Integrity ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add MATCH PARTIAL referential integrity}}<br />
<br />
{{TodoItem<br />
|Change foreign key constraint for array -&gt; element to mean element in array?<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-10/msg01814.php <nowiki>foreign keys for array/period contains relationships</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix problem when cascading referential triggers make changes on cascaded tables, seeing the tables in an intermediate state<br />
* [http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php <nowiki>Re: [PATCHES] Work-in-progress referential action trigger timing</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Are ri_KeysEqual checks in the RI enforcement triggers still necessary?<br />
* [http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php <nowiki>Re: Effects of cascading references in foreign keys</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Check Constraints ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Run check constraints only when affected columns are changed<br />
* http://archives.postgresql.org/message-id/1326055327.15293.13.camel@vanquo.pezone.net<br />
}}<br />
<br />
{{TodoItem<br />
|Do not scan the table when a check constraint is added in the same command that adds the column<br />
* [http://www.postgresql.org/message-id/CAMkU%3D1z5vXZ8Txd9_8hvNFovtbGuP4VTitFRN59XDncEHVGtJA@mail.gmail.com skip table scan for adding column with provable check constraints]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Server-Side Languages ==<br />
<br />
{{TodoItem<br />
|Add support for polymorphic arguments and return types to languages other than PL/PgSQL}}<br />
<br />
{{TodoItem<br />
|Add support for OUT and INOUT parameters to languages other than PL/PgSQL}}<br />
<br />
{{TodoItem<br />
|Add more fine-grained specification of functions taking arbitrary data types<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg00367.php <nowiki>RfD: more powerful &quot;any&quot; types</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow holdable cursors in SPI}}<br />
<br />
{{TodoItem<br />
|Rethink query plan caching and timing of parse analysis within SQL-language functions<br />
|They should work more like plpgsql functions do ...<br />
* [http://archives.postgresql.org/pgsql-bugs/2011-05/msg00078.php <nowiki>Re: BUG #6019: invalid cached plan on inherited table</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow regex operations in PL/Perl using UTF8 characters in non-UTF8 encoded databases}}<br />
<br />
=== PL/pgSQL ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]}}<br />
<br />
{{TodoItem<br />
|<nowiki>Allow listing of record column names, and access to record columns via variables, e.g. columns := r.(*), tval2 := r.(colname)</nowiki><br />
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php <nowiki>Re: PL/PGSQL: Dynamic Record Introspection</nowiki>]<br />
* [http://pgxn.org/dist/colnames/ <nowiki>colnames: Extension to retrieve column names from a record</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow row and record variables to be set to NULL constants, and allow NULL tests on such variables<br />
|Because a row is not scalar, do not allow assignment from NULL-valued scalars.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php <nowiki>NULL and plpgsql rows</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider keeping separate cached copies when search_path changes<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php <nowiki>pl/pgsql Plan Invalidation and search_path</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve handling of NULL row values vs. NULL rows<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg01758.php <nowiki>Null row vs. row of nulls in plpgsql</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg01973.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve PERFORM handling of WITH queries or document limitation<br />
* http://archives.postgresql.org/pgsql-bugs/2011-03/msg00309.php<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== PL/Python ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Create a new restricted execution class that will allow passing function arguments in as locals. Passing them as globals means functions cannot be called recursively.<br />
* [http://archives.postgresql.org/pgsql-hackers/2011-02/msg01468.php <nowiki>Re: pl/python do not delete function arguments</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add a DB-API compliant interface on top of the SPI interface<br />
* http://petereisentraut.blogspot.com/2011/11/plpydbapi-db-api-for-plpython.html<br />
}}<br />
<br />
{{TodoItem<br />
|For functions returning a setof record with a composite type, cache the I/O functions for the composite type<br />
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg02007.php<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Clients ==<br />
<br />
{{TodoItem<br />
|Split out pg_resetxlog output into pre- and post-sections<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg02040.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve pg_rewind<br />
* [https://www.postgresql.org/message-id/CAN-RpxDhc_8JOq%3DcT9vd6MqWQaS0ZtvSf2LFV1V+bjOoEz02ow@mail.gmail.com Proposal: pg_rewind to skip config files]<br />
}}<br />
<br />
=== psql ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Move psql backslash database information into the backend, use mnemonic commands?<br />
|This would allow non-psql clients to pull the same information out of the database as psql. <br />
* [http://archives.postgresql.org/pgsql-hackers/2004-01/msg00191.php <nowiki>Re: psql \d option list overloaded</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Make psql's \d commands distinguish default privileges from no privileges<br />
|ACL displays were visibly different for the two cases before we "improved" them by using array_to_string.<br />
* [http://archives.postgresql.org/pgsql-bugs/2011-05/msg00082.php <nowiki>BUG #6021: There is no difference between default and empty access privileges with \dp</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consistently display privilege information for all objects in psql}}<br />
<br />
{{TodoItem<br />
|Add a \set variable to control whether \s displays line numbers<br />
|Another option is to add \# which lists line numbers, and allows command execution.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php <nowiki>Re: psql possible TODO</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Include the symbolic SQLSTATE name in verbose error reports<br />
* [http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php <nowiki>Re: Checking is TSearch2 query is valid</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add option to wrap column values at whitespace boundaries, rather than chopping them at a fixed width.<br />
|Currently, &quot;wrapped&quot; format chops values into fixed widths. Perhaps the word wrapping could use the same algorithm documented in the W3C specification. <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php <nowiki>Re: psql wrapped format default for backslash-d commands</nowiki>]<br />
* http://www.w3.org/TR/CSS21/tables.html#auto-table-layout}}<br />
<br />
{{TodoItem<br />
|Add option to print advice for people familiar with other databases<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-01/msg01845.php <nowiki>MySQL-ism help patch for psql</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix FETCH_COUNT to handle SELECT ... INTO and WITH queries<br />
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg01565.php<br />
* http://archives.postgresql.org/pgsql-bugs/2010-05/msg00192.php<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent psql from sending remaining single-line multi-statement queries after reconnecting<br />
* http://archives.postgresql.org/pgsql-bugs/2010-05/msg00159.php<br />
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg01283.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve line drawing characters<br />
* http://archives.postgresql.org/pgsql-hackers/2011-04/msg00386.php<br />
}}<br />
<br />
{{TodoItem<br />
|Consider improving the continuation prompt<br />
* http://archives.postgresql.org/pgsql-hackers/2011-04/msg01772.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve speed of tab completion by using LIKE<br />
* http://www.postgresql.org/message-id/20120821174847.GL1267@tamriel.snowman.net<br />
}}<br />
<br />
{{TodoItem<br />
|Add handling of Unicode grapheme clusters<br />
* http://www.postgresql.org/message-id/Y8iMr2wi2ABrOSBH@momjian.us<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== pg_dump / pg_restore ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Dump security labels and comments on databases in a way that allows to load a dump into a differently named database<br />
* [http://www.postgresql.org/message-id/20150710115735.GH26521@alap3.anarazel.de security labels on databases are bad for dump & restore]<br />
|}}<br />
<br />
{{TodoItem<br />
|<nowiki>Add full object name to the tag field. eg. for operators we need '=(integer, integer)', instead of just '='.</nowiki>}}<br />
<br />
{{TodoItem<br />
|Avoid using platform-dependent names for locales in pg_dumpall output<br />
|Using native locale names puts roadblocks in the way of porting a dump to another platform. One possible solution is to get<br />
CREATE DATABASE to accept some agreed-on set of locale names and fix them up to meet the platform's requirements.<br />
* http://archives.postgresql.org/message-id/21396.1241716688@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
|In a selective dump, allow dumping of an object and all its dependencies}}<br />
<br />
{{TodoItem<br />
|Stop dumping CASCADE on DROP TYPE commands in clean mode}}<br />
<br />
{{TodoItem<br />
|Allow pg_restore to load different parts of the COPY data for a single table simultaneously}}<br />
<br />
{{TodoItem<br />
|Preserve sparse storage of large objects over dump/restore<br />
* [http://archives.postgresql.org/message-id/18789.1349750451@sss.pgh.pa.us <nowiki>TODO item: teach pg_dump about sparsely-stored large objects</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent PL/pgSQL comment from throwing an error in a non-superuser restore<br />
* [http://www.postgresql.org/message-id/E1VuYH7-0008Rz-SV@wrigleys.postgresql.org Reloading dump fails at COMMENT ON EXTENSION plpgsql]<br />
}}<br />
<br />
{{TodoItem<br />
|Delay REFRESH MATERIALIZED VIEW until dependent indexes are created<br />
* [http://www.postgresql.org/message-id/20140820021530.2534.43156@wrigleys.postgresql.org pg_restore unusable for expensive matviews]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== pg_upgrade ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Handle large object comments<br />
|This is difficult to do because the large object doesn't exist when --schema-only is loaded.<br />
}}<br />
<br />
{{TodoItem<br />
|Consider using pg_depend for checking object usage in version.c<br />
}}<br />
<br />
{{TodoItem<br />
|Migrate pg_statistic by dumping it out as a flat file, so analyze is not necessary<br />
* [http://archives.postgresql.org/message-id/CAAZKuFaWdLkK8eozSAooZBets9y_mfo2HS6urPAKXEPbd-JLCA@mail.gmail.com pg_upgrade and statistics]<br />
* [https://www.postgresql.org/message-id/20171205140135.GA25023%40momjian.us Speeding up pg_upgrade]<br />
}}<br />
<br />
{{TodoItem<br />
|Find cleaner way to start/stop dedicated servers for upgrades<br />
* http://archives.postgresql.org/pgsql-hackers/2012-08/msg00275.php<br />
}}<br />
<br />
{{TodoItem<br />
|Desired changes that would prevent upgrades with pg_upgrade<br />
* 32-bit page checksums<br />
* Add metapage to GiST indexes<br />
* Clean up hstore's internal representation<br />
* Remove tuple infomask bit HEAP_MOVED_OFF and HEAP_MOVED_IN<br />
* [http://www.postgresql.org/message-id/CAK+WP1xdmyswEehMuetNztM4H199Z1w9KWRHVMKzyyFM+hV%3DzA@mail.gmail.com fix char() index trailing space handling]<br />
* [http://www.postgresql.org/message-id/CAPpHfdtxXMjyZxwND09ZLBBACVbWb5J9bLUf67CndR4VKFDgwg@mail.gmail.com Use non-collation-aware comparisons for GIN opclasses]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== ecpg ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Docs<br />
|Document differences between ecpg and the SQL standard and information about the Informix-compatibility module.}}<br />
<br />
{{TodoItem<br />
|Solve cardinality &gt; 1 for input descriptors / variables?}}<br />
<br />
{{TodoItem<br />
|Add a semantic check level, e.g. check if a table exists}}<br />
<br />
{{TodoItem<br />
|fix handling of DB attributes that are arrays}}<br />
<br />
{{TodoItem<br />
|Fix nested C comments}}<br />
<br />
{{TodoItem<br />
|sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified}}<br />
<br />
{{TodoItem<br />
|Make SET CONNECTION thread-aware, non-standard?}}<br />
<br />
{{TodoItem<br />
|Allow multidimensional arrays}}<br />
<br />
{{TodoItem<br />
|Implement COPY FROM STDIN}} <br />
<br />
{{TodoItem<br />
|Provide a way to specify size of a bytea parameter<br />
* [http://archives.postgresql.org/message-id/200906192131.n5JLVoMo044178@wwwmaster.postgresql.org <nowiki>BUG #4866: ECPG and BYTEA</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow reuse of cursor name variables<br />
* [http://archives.postgresql.org/message-id/20100329113435.GA3430@feivel.credativ.lan <nowiki>Problems with variable cursorname in ecpg</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== libpq ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add PQexecf() that allows complex parameter substitution<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php <nowiki>Last minute mini-proposal (I know, know) for PQexecf()</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add SQLSTATE and severity to errors generated within libpq itself<br />
* [http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php <nowiki>v8.1: Error severity on libpq PGconn*</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01425.php<br />
}}<br />
<br />
{{TodoItem<br />
|Add support for interface/ipaddress binding to libpq<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg01811.php <nowiki>SR/libpq - outbound interface/ipaddress binding</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|When receiving a FATAL error remember it, so that it doesn't profess ingnorance about why the session was closed<br />
* [http://www.postgresql.org/message-id/CA+TgmoZ4P1cQetjOxQoHiG072UcE7dpE7dTBV8hMOidhwhof+g@mail.gmail.com<nowiki>Idle In Transaction Session Timeout, revived</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Pipelining support for libpq async API and an array-valued PQexecPrepared that uses it<br />
* [http://www.postgresql.org/message-id/CAMsr+YHE8Rt800yWcHEL8SrgruK0ng_nBmtKV6YMZ2BAzRBZzw@mail.gmail.com Foreign table batched inserts]<br />
}}<br />
{{TodoEndSubsection}}<br />
<br />
== Triggers ==<br />
<br />
{{TodoItem<br />
|Improve storage of deferred trigger queue<br />
|Right now all deferred trigger information is stored in backend memory. This could exhaust memory for very large trigger queues. This item involves dumping large queues into files, or doing some kind of join to process all the triggers, some bulk operation, or a bitmap. <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php <nowiki>Re: BUG #4204: COPY to table with FK has memory leak</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-10/msg00464.php <nowiki>Scaling up deferred unique checks and the after trigger queue</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2011-08/msg00023.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow triggers to be disabled in only the current session.<br />
|This is currently possible by starting a multi-statement transaction, modifying the system tables, performing the desired SQL, restoring the system tables, and committing the transaction. ALTER TABLE ... TRIGGER requires a table lock so it is not ideal for this usage.}}<br />
<br />
{{TodoItem<br />
|With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY<br />
|If the dump is known to be valid, allow foreign keys to be added without revalidating the data.}}<br />
<br />
{{TodoItem<br />
|When statement-level triggers are defined on a parent table, have them fire only on the parent table, and fire child table triggers only where appropriate<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg01883.php <nowiki>Statement-level triggers and inheritance</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Tighten trigger permission checks<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php <nowiki>Security leak with trigger functions?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow BEFORE INSERT triggers on views<br />
* [http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php <nowiki>Re: Why can't I put a BEFORE EACH ROW trigger on a view?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add database and transaction-level triggers<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php <nowiki>Proposal for db level triggers</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00620.php <nowiki>triggers on prepare, commit, rollback... ?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid requirement for AFTER trigger functions to return a value<br />
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg02384.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow creation of inline triggers<br />
* http://archives.postgresql.org/pgsql-hackers/2012-02/msg00708.php<br />
}}<br />
<br />
== Inheritance ==<br />
<br />
{{TodoItem<br />
|Allow unique indexes across inherited tables (requires multi-table indexes)<br />
* Postgres 11 allows unique indexes across partitions if the partition key is part of the index.<br />
}}<br />
<br />
{{TodoItem<br />
|Research whether ALTER TABLE / SET SCHEMA should work on inheritance hierarchies (and thus support ONLY)}}<br />
<br />
{{TodoItem<br />
|ALTER TABLE variants sometimes support recursion and sometimes not, but this is poorly/not documented, and the ONLY marker would then be silently ignored. Clarify the documentation, and reject ONLY if it is not supported.}}<br />
<br />
== Indexes ==<br />
<br />
{{TodoItem<br />
|Prevent index uniqueness checks when UPDATE does not modify the column<br />
|Uniqueness (index) checks are done when updating a column even if the column is not modified by the UPDATE.<br />
However, HOT already short-circuits this in common cases, so more work might not be helpful.<br />
* http://www.postgresql.org/message-id/CA+TgmoZOyaTanfEvNUdiHBCuu9Zh0JVP1e_UTVbx6Rvj9vFC9Q@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Consider having a larger statistics target for indexed columns and expression indexes. <br />
}}<br />
<br />
{{TodoItem<br />
|Allow multiple indexes to be created concurrently, ideally via a single heap scan<br />
|pg_restore allows parallel index builds, but it is done via subprocesses, and there is no SQL interface for this.<br />
Cluster could definitely benefit from this.<br />
* http://archives.postgresql.org/pgsql-performance/2011-04/msg00093.php<br />
* http://www.postgresql.org/message-id/CADVWZZJ5AS%3DXVrDwfTQqQP_V1+_fTYcZhq%3Dd5CbCXoALCjObbg@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Consider sorting entries before inserting into btree index<br />
* [http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php <nowiki>Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider using "effective_io_concurrency" for index scans<br />
|Currently only bitmap scans use this, which might be fine because most multi-row index scans use bitmap scans.<br />
* [http://www.postgresql.org/message-id/CAGTBQpZzf70n0PYJ%3DVQLd+jb3wJGo%3D2TXmY+SkJD6G_vjC5QNg@mail.gmail.com Prefetch index pages for B-Tree index scans]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow GIN indexes to be used for exclusion constraints<br />
* http://archives.postgresql.org/pgsql-hackers/2012-05/msg00669.php<br />
}}<br />
<br />
{{TodoItem<br />
| Allow "loose" or "skip" scans on btree indexes in which the first column has low cardinality<br />
* http://archives.postgresql.org/pgsql-performance/2012-08/msg00159.php<br />
}}<br />
<br />
{{TodoItem<br />
| Make the planner's "special index operator" mechanism extensible<br />
* http://www.postgresql.org/message-id/27270.1364700924@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
| Allow index-only COUNT(*) for indexes which don't support index-only scans<br />
}}<br />
<br />
{{TodoItem<br />
|Improve GIN performance<br />
* [http://www.postgresql.org/message-id/52F373CC.4050800@vmware.com Small GIN optimizations (after 9.4)]<br />
}}<br />
<br />
{{TodoItem<br />
| Teach GIN cost estimation about "fast scans"<br />
* http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com<br />
}}<br />
<br />
{{TodoItem<br />
| Allow unlogged indexes<br />
* http://www.postgresql.org/message-id/11561.1414793261@sss.pgh.pa.us<br />
}}<br />
<br />
=== GIST ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add more GIST index support for geometric data types}}<br />
<br />
{{TodoItem<br />
|Allow GIST indexes to create more complex index types, like digital trees (see Aoki)}}<br />
<br />
{{TodoItem<br />
|Fix performance issues in contrib/seg and contrib/cube GiST support<br />
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904161633160.4053@aragorn.flymine.org GiST index performance]<br />
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904221704470.22330@aragorn.flymine.org draft patch]<br />
* [http://archives.postgresql.org/pgsql-performance/2009-05/msg00069.php <nowiki>Re: GiST index performance</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-performance/2009-06/msg00068.php <nowiki>GiST index performance</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|[http://archives.postgresql.org/message-id/4DC8D284-05CF-4E3D-9670-AC9A32C37A36@justatheory.com GiST index support for arrays]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Hash ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add UNIQUE capability to hash indexes<br />
* [https://www.postgresql.org/message-id/592254A5.9000809@anastigmatix.net Re: PG10 Crash-safe and replicable Hash Indexes and UNIQUE]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow multi-column hash indexes<br />
* This requires all columns to be specified for a query to use the index.<br />
* [https://www.postgresql.org/message-id/CA+Tgmoax6DhnKsuE_gzY5qkvmPEok77JAP1h8wOTbf+dg2Ycrw@mail.gmail.com Write Ahead Logging for Hash Indexes]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Sorting ==<br />
<br />
{{TodoItem<br />
|Consider detoasting keys before sorting}}<br />
<br />
{{TodoItem<br />
|Allow sorts of skinny tuples to use even more available memory.<br />
|Now that it is not limited by MaxAllocSize, don't limit by INT_MAX either.<br />
* [http://www.postgresql.org/message-id/CA+U5nMKkRMin1pV8VMpS6_n7hcOWSG0kZS3oFL9JOa8DV6vJyQ@mail.gmail.com Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize]<br />
}}<br />
<br />
== Cache Usage ==<br />
<br />
{{TodoItem<br />
|Consider automatic caching of statements at various levels:<br />
* Parsed query tree<br />
* Query execute plan<br />
* Query results <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php <nowiki>Cached Query Plans (was: global prepared statements)</nowiki>]<br />
* [https://www.postgresql.org/message-id/CAFj8pRAGLaiEm8ur5DWEBo7qHRWTk9HxkuUAz00CZZtJj-LkCA%40mail.gmail.com PoC plpgsql - possibility to force custom or generic plan]<br />
* [https://www.postgresql.org/message-id/CADT4RqAd_74m6MUbXAPsYzqXG3F6wWVhS_dFJijrfXs7N+QGHQ@mail.gmail.com Cached/global query plans, autopreparation]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider allowing higher priority queries to have referenced shared buffer pages stay in memory longer<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php <nowiki>Re: How to keep a table in memory?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix memory leak caused by negative catcache entries<br />
* [http://www.postgresql.org/message-id/51C0A1FF.2050404@vmware.com <nowiki>Re: Memory leak in PL/pgSQL function which CREATE/SELECT/DROP a temporary table</nowiki>]<br />
* [https://www.postgresql.org/message-id/flat/20161219.201505.11562604.horiguchi.kyotaro@lab.ntt.co.jp <nowiki>Protect syscache from bloating with negative cache entries</nowiki>]<br />
}}<br />
<br />
== Vacuum ==<br />
<br />
{{TodoItem<br />
|Consider having single-page pruning update the visibility map<br />
* <nowiki>https://commitfest.postgresql.org/action/patch_view?id=75</nowiki><br />
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg02344.php <nowiki>Re: visibility maps and heap_prune</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow VACUUM FULL and CLUSTER to update the visibility map<br />
* https://www.postgresql.org/message-id/CAPpHfdtcxUVys6r6JqX2s%2B5CowXDKMOnfcJoJWHyjWDe%3DhwHMw%40mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Improve tracking of total relation tuple counts now that vacuum doesn't always scan the whole heap<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00531.php Partial vacuum versus pg_class.reltuples]<br />
}}<br />
<br />
{{TodoItem<br />
|Bias FSM towards returning free space near the beginning of the heap file, in hopes that empty pages at the end can be truncated by VACUUM<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg01124.php <nowiki>FSM search modes</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add a way to compact tables without exclusive locking, similar to pre-9.0 VACUUM FULL<br />
* [http://www.postgresql.org/message-id/20150424190403.GP4369@alvh.no-ip.org Re: Feedback on getting rid of VACUUM FULL]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider a more compact data representation for dead tuple locations within VACUUM<br />
* https://www.postgresql.org/message-id/flat/CAD21AoAfOZvmfR0j8VmZorZjL7RhTiQdVttNuC4W-Shdc2a-AA%40mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Provide more information in order to improve user-side estimates of dead space bloat in relations<br />
* [http://archives.postgresql.org/pgsql-general/2009-05/msg01039.php <nowiki>Re: Bloated Table</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce the number of table scans performed by vacuum<br />
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg01119.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg00624.php<br />
}}<br />
<br />
{{TodoItem<br />
|Vacuum Gin indexes in physically order rather than logical order<br />
* http://archives.postgresql.org/pgsql-hackers/2012-04/msg00443.php<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid creation of the free space map for small tables<br />
* http://archives.postgresql.org/pgsql-hackers/2011-11/msg01751.php<br />
}}<br />
<br />
=== Auto-vacuum ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Issue log message to suggest VACUUM FULL if a table is nearly empty?<br />
*[http://www.postgresql.org/message-id/F40B0968DB0A904DA78A924E633BE78645FAAF@SYDEXCHTMP2.au.fjanz.com discussion]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent long-lived temporary tables from causing frozen-xid advancement starvation<br />
|The problem is that autovacuum cannot vacuum them to set frozen xids; only the session that created them can. <br />
* [http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php <nowiki>Re: AutoVacuum Behaviour Question</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent autovacuum from running if an old transaction is still running from the last vacuum<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php <nowiki>Re: Autovacuum and OldestXmin</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Have autoanalyze of parent tables occur when child tables are modified<br />
* http://archives.postgresql.org/pgsql-performance/2010-06/msg00137.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow visibility map all-visible bits to be set even when an auto-ANALYZE is running<br />
* http://archives.postgresql.org/pgsql-hackers/2012-01/msg00356.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve autoanalyze thresholds for small tables<br />
* http://www.postgresql.org/message-id/5078AD6B.8060802@agliodbs.com<br />
}}<br />
<br />
{{TodoItem<br />
|Make autovacuum scheduling smarter<br />
* https://www.postgresql.org/message-id/0A3221C70F24FB45833433255569204D1F8A4DC6%40G01JPEXMBYT05<br />
* https://www.postgresql.org/message-id/CAD21AoBUaSRBypA6pd9ZD%3DU-2TJCHtbyZRmrS91Nq0eVQ0B3BA%40mail.gmail.com<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Locking ==<br />
<br />
{{TodoItem<br />
|Fix problem when multiple subtransactions of the same outer transaction hold different types of locks, and one subtransaction aborts<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php <nowiki>FOR SHARE vs FOR UPDATE locks</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php <nowiki>Re: FOR SHARE vs FOR UPDATE locks</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php <nowiki>Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php <nowiki>Re: savepoints and upgrading locks</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve deadlock detection when a page cleaning lock conflicts with a shared buffer that is pinned<br />
* [http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php <nowiki>BUG #3883: Autovacuum deadlock with truncate?</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php <nowiki>Thoughts about bug #3883</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php <nowiki>Re: pgsql: Add checks to TRUNCATE, CLUSTER, and REINDEX to prevent</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Detect deadlocks involving LockBufferForCleanup()<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php <nowiki>Thoughts about bug #3883</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow finer control over who is cancelled in a deadlock<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01727.php<br />
}}<br />
<br />
== Startup Time Improvements ==<br />
<br />
{{TodoItem<br />
|Allow backends to change their database without restart<br />
|This allows for faster server startup.<br />
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg00843.php<br />
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg00336.php<br />
}}<br />
<br />
== Write-Ahead Log ==<br />
<br />
{{TodoItem<br />
|Eliminate need to write full pages to WAL before page modification<br />
|Currently, to protect against partial disk page writes, we write full page images to WAL before they are modified so we can correct any partial page writes during recovery. These pages can also be eliminated from point-in-time archive files. <br />
* [http://archives.postgresql.org/pgsql-hackers/2002-06/msg00655.php <nowiki>Re: Index Scans become Seq Scans after VACUUM ANALYSE</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg01191.php<br />
* [http://archives.postgresql.org/message-id/20120105061916.GB21048@fetter.org WIP double writes]<br />
* [http://archives.postgresql.org/message-id/4EFC449F02000025000441CD@gw.wicourts.gov double writes]<br />
* [http://archives.postgresql.org/message-id/20120110214344.GB21106@fetter.org Double-write with Fast Checksums]<br />
* [http://archives.postgresql.org/message-id/1962493974.656458.1327703514780.JavaMail.root@zimbra-prod-mbox-4.vmware.com double writes using "double-write buffer" approach]<br />
* http://archives.postgresql.org/pgsql-hackers/2012-10/msg01463.php<br />
}}<br />
<br />
{{TodoItem<br />
|When full page writes are off, write CRC to WAL and check file system blocks on recovery<br />
|If CRC check fails during recovery, remember the page in case a later CRC for that page properly matches. The difficulty is that hint bits are not WAL logged, meaning a valid page might not match the earlier CRC.}}<br />
<br />
{{TodoItem<br />
|Write full pages during file system write and not when the page is modified in the buffer cache<br />
|This allows most full page writes to happen in the background writer. It might cause problems for applying WAL on recovery into a partially-written page, but later the full page will be replaced from WAL.<br />
* [http://archives.postgresql.org/message-id/CAGvK12UST-tPhyLrSLuSpwFxZbAO79yYrhV2xaLmS2MkUxNUVQ@mail.gmail.com Page Checksums + Double Writes]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow WAL information to recover corrupted pg_controldata<br />
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php <nowiki>Re: [HACKERS] pg_resetxlog -r flag</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Speed WAL recovery by allowing more than one page to be prefetched<br />
|This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay. <br />
* [http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php <nowiki>Slow PITR restore</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php <nowiki>Re: [GENERAL] Slow PITR restore</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php <nowiki>Read-ahead and parallelism in redo recovery</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve WAL concurrency by increasing lock granularity<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php <nowiki>Reworking WAL locking</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Have resource managers report the duration of their status changes<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php <nowiki>Recovery of Multi-stage WAL actions</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Close deleted WAL files held open in *nix by long-lived read-only backends<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php <nowiki>Deleted WAL files held open by backends in Linux</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php <nowiki>Re: Deleted WAL files held open by backends in Linux</nowiki>]<br />
}}<br />
<br />
== Optimizer / Executor ==<br />
<br />
{{TodoItem<br />
|Improve selectivity functions for geometric operators}}<br />
<br />
{{TodoItem<br />
|Consider adding a useful and convenient way of seeing paths rejected by the planner. OPTIMIZER_DEBUG does this so some extent but it seemingly gets very little use and must be enabled during compilation.<br />
* http://archives.postgresql.org/pgsql-hackers/2012-08/msg00597.php<br />
* https://postgr.es/m/1fd8e494-4740-4108-6d06-d5a173836047@gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Log statements where the optimizer row estimates were dramatically different from the number of rows actually found?}}<br />
<br />
{{TodoItem<br />
|Consider compressed annealing to search for query plans<br />
|This might replace GEQO.<br />
* http://archives.postgresql.org/message-id/15658.1241278636%40sss.pgh.pa.us<br />
}}<br />
<br />
=== Hashing ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow single batch hash joins to preserve outer pathkeys<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg00806.php Re: Potential Join Performance Issue]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid building the same hash table more than once during the same query<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid hashing for distinct and then re-hashing for hash join<br />
* [http://archives.postgresql.org/message-id/4136ffa0902191346g62081081v8607f0b92c206f0a@mail.gmail.com Re: Fixing Grittner's planner issues]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Background Writer ==<br />
<br />
{{TodoItem<br />
|Consider having the background writer update the transaction status hint bits before writing out the page<br />
|Implementing this requires the background writer to have access to system catalogs and the transaction status log.<br />
* [http://www.postgresql.org/message-id/CAMkU%3D1zf1Yo0dYJzJ-pk9o4mwLuMD4Uzw6Jck7u1nC_Xb2gYWA@mail.gmail.com Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider adding buffers the background writer finds reusable to the free list <br />
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php <nowiki>Background LRU Writer/free list</nowiki>]<br />
* [http://archives.postgresql.org/message-id/CA+U5nMKtvyDcV4zTr7bq7t6cA2nBfLxCJ8tQgVBnc5ddRPO+Bg@mail.gmail.com our buffer replacement strategy is kind of lame]<br />
* [http://www.postgresql.org/message-id/CAOeZVic4HikhmzVD%3DZP4JY9g8PgpyiQQOXOELWP%3DkR+%3DH1Frgg@mail.gmail.com Page replacement algorithm in buffer cache]<br />
* [http://www.postgresql.org/message-id/002f01ce50a8$e057c7a0$a10756e0$@kapila@huawei.com Move unused buffers to freelist]<br />
}}<br />
<br />
{{TodoItem<br />
|Automatically tune bgwriter_delay based on activity rather then using a fixed interval<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php <nowiki>Background LRU Writer/free list</nowiki>]<br />
* [http://archives.postgresql.org/message-id/CA+U5nMKtvyDcV4zTr7bq7t6cA2nBfLxCJ8tQgVBnc5ddRPO+Bg@mail.gmail.com our buffer replacement strategy is kind of lame]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider whether increasing BM_MAX_USAGE_COUNT improves performance<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php <nowiki>Bgwriter LRU cleaning: we've been going at this all wrong</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency<br />
* [http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php <nowiki>Re: Load Distributed Checkpoints, final patch</nowiki>]<br />
}}<br />
<br />
== Concurrent Use of Resources ==<br />
<br />
{{TodoItem<br />
|Do async I/O for faster random read-ahead of data<br />
|Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php <nowiki>Asynchronous I/O Support</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php <nowiki>Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php <nowiki>There's random access and then there's random access</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php <nowiki>Bitmap index scan preread using posix_fadvise (Was: There's random access and then there's random access)</nowiki>]<br />
The above patch is already applied as of 8.4, but it still remains to figure out how to handle plain indexscans effectively.<br />
* [http://archives.postgresql.org//pgsql-hackers/2009-01/msg00806.php Problems with the patch submitted for posix_fadvise in index scans]<br />
}}<br />
<br />
{{TodoItem<br />
|SMP scalability improvements<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php <nowiki>Straightforward changes for increased SMP scalability</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php <nowiki>Re: Reducing Transaction Start/End Contention</nowiki>]<br />
}}<br />
<br />
== TOAST ==<br />
<br />
{{TodoItem<br />
|Allow user configuration of TOAST thresholds<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php <nowiki>Re: Proposed adjustments in MaxTupleSize and toastthresholds</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php <nowiki>pg_lzcompress strategy parameters</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce unnecessary cases of deTOASTing<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php <nowiki>Re: [PATCHES] Eliminate more detoast copies for packed varlenas</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce costs of repeat de-TOASTing of values<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg01096.php <nowiki>WIP patch: reducing overhead for repeat de-TOASTing</nowiki>]<br />
}}<br />
<br />
== Monitoring ==<br />
<br />
{{TodoItem<br />
|Have pg_stat_activity display query strings in the correct client encoding<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-01/msg00131.php <nowiki>pg_stats queries versus per-database encodings</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
| Allow reporting of stalls due to wal_buffer wrap-around<br />
* http://archives.postgresql.org/pgsql-hackers/2012-02/msg00826.php<br />
}}<br />
<br />
{{TodoItem<br />
| Restructure pg_stat_database columns tup_returned and tup_fetched to return meaningful values<br />
* http://www.postgresql.org/message-id/20121012060345.GA29214@toroid.org<br />
}}<br />
<br />
{{TodoItem<br />
| Improve handling of pg_stat_statements handling of bind "IN" variables<br />
* [http://www.postgresql.org/message-id/CAM3SWZSpdPB3uErnXWMt3q74y0r+84ZsOt2U3HKKes_V7O+0Qg@mail.gmail.com Revisiting pg_stat_statements and IN()]<br />
}}<br />
<br />
== Miscellaneous Performance ==<br />
<br />
{{TodoItem<br />
|Rather than consider mmap()-ing in 8k pages, consider mmap()'ing entire files into a backend?<br />
|Doing I/O to large tables would consume a lot of address space or require frequent mapping/unmapping. Extending the file also causes mapping problems that might require mapping only individual pages, leading to thousands of mappings. Another problem is that there is no way to _prevent_ I/O to disk from the dirty shared buffers so changes could hit disk before WAL is written.<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01239.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow configuration of backend priorities via the operating system<br />
|Though backend priorities make priority inversion during lock waits possible, research shows that this is not a huge problem.<br />
* [http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php <nowiki>Priorities for users or queries?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider if CommandCounterIncrement() can avoid its AcceptInvalidationMessages() call<br />
* [http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php <nowiki>pgsql: Avoid incrementing the CommandCounter when</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider Cartesian joins when both relations are needed to form an indexscan qualification for a third relation<br />
* [http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php <nowiki>Re: TB-sized databases</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider not storing a NULL bitmap on disk if all the NULLs are trailing<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php <nowiki>Proposal for Null Bitmap Optimization(for Trailing NULLs)</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php <nowiki>Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Sort large UPDATE/DELETEs so it is done in heap order<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php <nowiki>Possible future performance improvement: sort updates/deletes by ctid</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add auto-tuning of work_mem<br />
* [http://www.postgresql.org/message-id/20131009143046.GT22450@momjian.us Auto-tuning work_mem and maintenance_work_mem]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider decreasing the I/O caused by updating tuple hint bits<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00847.php <nowiki>Hint Bits and Write I/O</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-07/msg00199.php <nowiki>Re: [HACKERS] Hint Bits and Write I/O</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg00695.php<br />
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg00792.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-01/msg01063.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01408.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01453.php<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid reading in b-tree pages when replaying vacuum records in hot standby mode<br />
* [http://archives.postgresql.org/message-id/1272571938.4161.14739.camel@ebony <nowiki>Hot Standby tuning for btree_xlog_vacuum()</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Restructure truncation logic to be more resistant to failure<br />
|This also involves not writing dirty buffers for a truncated or dropped relation<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01032.php<br />
}}<br />
<br />
{{TodoItem<br />
|Enhance foreign data wrappers, parallelism, partitioning, and perhaps add a global snapshot/transaction manager to allow creation of a proof-of-concept built-in sharding solution<br />
|Ideally these enhancements and new facilities will be available to external sharding solutions as well.<br />
* [https://wiki.postgresql.org/wiki/Built-in_Sharding Built-in sharding wiki]<br />
}}<br />
<br />
== Miscellaneous Other ==<br />
<br />
{{TodoItem<br />
|Deal with encoding issues for filenames in the server filesystem<br />
* {{MessageLink|20090413184335.39BE.52131E4D@oss.ntt.co.jp|a proposed patch here}}<br />
* {{MessageLink|8484.1244655656@sss.pgh.pa.us|some issues about it here}}<br />
* {{MessageLink|20100107103740.97A5.52131E4D@oss.ntt.co.jp|Windows-specific patch here}}<br />
}}<br />
<br />
{{TodoItem<br />
|Deal with encoding issues in the output of localeconv()<br />
* [http://archives.postgresql.org/message-id/40c6d9160904210658y590377cfw6dbbecb53d2b8be0@mail.gmail.com bug report]<br />
* [http://archives.postgresql.org/message-id/49EF8DA0.90008@tpf.co.jp draft patch]<br />
* [http://archives.postgresql.org/message-id/21710.1243620986@sss.pgh.pa.us review of patch]<br />
}}<br />
<br />
{{TodoItem<br />
|Provide schema name and other fields available from SQL GET DIAGNOSTICS in error reports<br />
* [http://archives.postgresql.org/message-id/dcc563d10810211907n3c59a920ia9eb7cd2a6d5ea58@mail.gmail.com <nowiki>How to get schema name which violates fk constraint</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg00846.php <nowiki>patch - Report the schema along table name in a referential failure error message</nowiki>]<br />
* {{MessageLink|3191.1263306359@sss.pgh.pa.us|Re: NOT NULL violation and error-message}}<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-08/msg00213.php <nowiki>the case for machine-readable error fields</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Use sa_mask to close race conditions between signal handlers<br />
* http://www.postgresql.org/message-id/20130911013107.GA225735@tornado.leadboat.com<br />
}}<br />
<br />
{{TodoItem<br />
|Allow pg_export_snapshot() to run on hot standby servers<br />
|This will allow parallel pg_dump on such servers.<br />
* [http://www.postgresql.org/message-id/CA+U5nML2VMJ3R2YBAZ+CsAsTWF3LuYSo16Wu9+yXFrfy4%3Df2fA@mail.gmail.com pg_export_snapshot on standby side]<br />
}}<br />
<br />
{{TodoItem<br />
|Provide a way to enumerate and unregister background workers<br />
|Right now the only way to unregister bgworkers is from within the worker with <tt>proc_exit(0)</tt> or registering with <tt>BGW_NEVER_RESTART</tt><br />
* https://www.postgresql.org/message-id/CAMsr%2BYG-fD%2BmP-BNZDheVYucC7%3DoUn8ByTQSFz7RKkVX2MRS2Q%40mail.gmail.com<br />
}}<br />
<br />
== Source Code ==<br />
<br />
{{TodoItem<br />
|Rationalize division of labor between initdb and bootstrap<br />
* [https://www.postgresql.org/message-id/20220216021219.ygzrtb3hd5bn7olz%40alap3.anarazel.de <nowiki>initdb / bootstrap design</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow cross-compiling by generating the zic database on the target system}}<br />
<br />
{{TodoItem<br />
|Improve NLS maintenance of libpgport messages linked onto applications}}<br />
<br />
{{TodoItem<br />
|Use UTF8 encoding for NLS messages so all server encodings can read them properly}}<br />
<br />
{{TodoItem<br />
|Allow creation of universal binaries for Darwin<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00884.php <nowiki>Getting to universal binaries for Darwin</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider GnuTLS if OpenSSL license becomes a problem<br />
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg00892.php<br />
* [http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php <nowiki>[PATCH] Add support for GnuTLS</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php <nowiki>TODO: GNU TLS</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider making NAMEDATALEN more configurable<br />
|There is demand for making 128 the default, but there are also concerns about storage and memory usage and performance. So a rearchitecting to make the storage variable-length might be preferred.<br />
* Discussions when it was changed from 32 to 64: [https://www.postgresql.org/message-id/flat/003901c1b4ca%241d762500%248001a8c0%40jester] [https://www.postgresql.org/message-id/flat/1019615774.84994.11.camel%40knight.zort.ca] [https://www.postgresql.org/message-id/flat/D90A5A6C612A39408103E6ECDD77B82920CE98%40voyager.corporate.connx.com] [https://www.postgresql.org/message-id/flat/01C273A8.DA59BF90.jochen.westland%40invigo.de]<br />
* [https://www.postgresql.org/message-id/flat/1499106661641-5969858.post%40n3.nabble.com <nowiki>Revisiting NAMEDATALEN</nowiki>]<br />
* [https://www.postgresql.org/message-id/flat/CALSd-crdmj9PGdvdioU%3Da5W7P%3DTgNmEB2QP9wiF6DTUbBuMXrQ%40mail.gmail.com <nowiki>NAMEDATALEN increase because of non-latin languages</nowiki>] (contains ideas about variable-length storage)<br />
}}<br />
<br />
{{TodoItem<br />
|Research use of signals and sleep wake ups<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php <nowiki>Restartable signals 'n all that</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider simplifying how memory context resets handle child contexts<br />
* [http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php <nowiki>Re: Memory leak in nodeAgg</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Implement the non-threaded Avahi service discovery protocol<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00939.php <nowiki>Re: [PATCHES] Avahi support for Postgresql</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00097.php <nowiki>Re: Avahi support for Postgresql</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg01211.php <nowiki>Re: [PATCHES] Avahi support for Postgresql</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-04/msg00001.php <nowiki>Re: [HACKERS] Avahi support for Postgresql</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce data row alignment requirements on some 64-bit systems<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00369.php <nowiki>[WIP] Reduce alignment requirements on 64-bit systems.</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Restructure TOAST internal storage format for greater flexibility<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg00049.php <nowiki>Re: PG_PAGE_LAYOUT_VERSION 5 - time for change</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
| Consider removing the attribute options cache<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg00039.php<br />
}}<br />
<br />
{{TodoItem<br />
| Restructure /contrib section<br />
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg00705.php<br />
}}<br />
<br />
=== Windows ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Remove configure.in check for link failure when the cause is found}}<br />
<br />
{{TodoItem<br />
|Allow psql to use readline once non-US code pages work with backslashes}}<br />
<br />
{{TodoItem<br />
|Improve signal handling<br />
* [http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php <nowiki>Simplify Win32 Signaling code</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Support PGXS when using MSVC}}<br />
<br />
{{TodoItem<br />
|Fix MSVC NLS support, like for to_char()<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php <nowiki>NLS on MSVC strikes back!</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php <nowiki>Fix for 8.3 MSVC locale (Was [HACKERS] NLS on MSVC strikes back!)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix global namespace issues when using multiple terminal server sessions<br />
* [http://archives.postgresql.org/message-id/48F3BFCC.8030107@dunslane.net problems with Windows global namespace]}}<br />
<br />
{{TodoItem<br />
|Change from the current autoconf/gmake build system to cmake<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg01869.php <nowiki>About CMake (was Re: [COMMITTERS] pgsql: Append major version number and for libraries soname major)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve consistency of path separator usage<br />
* http://archives.postgresql.org/message-id/49C0BDC5.4010002@hagander.net<br />
}}<br />
<br />
{{TodoItem<br />
|Fix cross-compiling on Windows<br />
* http://archives.postgresql.org/pgsql-bugs/2010-10/msg00110.php<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce file statistics overhead on directory reads<br />
* http://www.postgresql.org/message-id/1338325561.82125.YahooMailNeo@web39304.mail.mud.yahoo.com<br />
}}<br />
<br />
{{TodoItem<br />
|Fix hang with long file paths<br />
* [http://www.postgresql.org/message-id/CAA4eK1JxaBofxpcgLqCx9EB%3Dm3PaXr9iFU9%3DV3ddDswsPZooxw@mail.gmail.com Long paths for tablespace leads to uninterruptible hang in Windows]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Wire Protocol Changes / v4 Protocol ===<br />
{{TodoSubsection}}<br />
<br />
<br />
{{TodoItem<br />
|Allow dynamic character set handling}}<br />
<br />
{{TodoItem<br />
|Ensure the client can determine the encoding of messages sent early in the handshake<br />
* http://www.postgresql.org/message-id/541A5659.5050006@2ndquadrant.com}}<br />
<br />
{{TodoItem<br />
|Let the client indicate character encoding of database names, user names, passwords, and of pre-auth error messages returned by the server<br />
* http://www.postgresql.org/message-id/16160.1360540050@sss.pgh.pa.us<br />
* http://www.postgresql.org/message-id/20131220030725.GA1411150@tornado.leadboat.com<br />
}}<br />
<br />
{{TodoItem<br />
|Send numeric version to clients in fixed header<br />
* [https://commitfest.postgresql.org/10/752/ <nowiki>patch to send server_version_num in v3 protocol as GUC_REPORT</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add decoded type length/precision (i.e. typmod information)}}<br />
<br />
{{TodoItem<br />
|Mark result columns as known-not-null when possible<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-11/msg01029.php <nowiki>Adding nullable indicator to Describe</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Use compression<br />
|Specify and implement wire protocol compression. If SSL transparent compression is used, hopefully avoid the overhead of key negotiation and encryption when SSL is configured only for compression. Note that [https://www.ietf.org/mail-archive/web/tls/current/msg11619.html compression is being removed from TLS 1.3] so we really need to do it ourselves.<br />
* http://archives.postgresql.org/pgsql-hackers/2012-06/msg00793.php<br />
}}<br />
<br />
{{TodoItem<br />
|Update clients to use data types, typmod, schema.table.column names of result sets using new statement protocol}}<br />
<br />
{{TodoItem<br />
|Set protocol for wire format negotiation<br />
* [http://archives.postgresql.org/message-id/CACMqXCKkGrGXxQhjHCKCe0B8hn6sTt-1sdgHZOSGQMxrusOsQA@mail.gmail.com GUC_REPORT for protocol tunables]<br />
}}<br />
<br />
{{TodoItem<br />
|Make sure upgrading to a 4.1 protocol version will actually work smoothly<br />
* [http://archives.postgresql.org/message-id/28307.1318255008@sss.pgh.pa.us Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow multi-state authentication (e.g. try client peer, fall back to md5)<br />
* http://www.postgresql.org/message-id/51A44185.5060306@2ndquadrant.com<br />
* http://www.postgresql.org/message-id/55192AFE.6080106@iki.fi<br />
* http://www.postgresql.org/message-id/54DB1D4E.8090700@vmware.com<br />
* https://commitfest.postgresql.org/6/320/<br />
}}<br />
<br />
{{TodoItem<br />
|Allow re-authentication<br />
|Let the client request re-authentication as a different user mid session, for connection pools that pass through the handshake.<br />
}}<br />
<br />
{{TodoItem<br />
|Identify the affected object in CommandComplete message?<br />
* http://www.postgresql.org/message-id/CAAfz9KNGVoyM+z_2tnPKTDXG_RdR9a33Y5s+zQ9LdwTTsqqZng@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Allow negotiation of encryption, <tt>STARTTLS</tt> style, rather than forcing client to decide on SSL or !SSL before connecting<br />
* http://www.postgresql.org/message-id/5406EAD3.7070002@2ndquadrant.com}}<br />
<br />
{{TodoItem<br />
|Permit lazy fetches of large values, at least out-of-line TOASTED values<br />
* http://www.postgresql.org/message-id/53FF0EF8.100@2ndquadrant.com<br />
}}<br />
<br />
{{TodoItem<br />
|Add session-level whitelisting of types for binary-mode transfer<br />
* http://www.postgresql.org/message-id/30470.1412055068@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
|Send client the xid when it is allocated<br />
|Lets the client later ask the server "did this commit or not?" after interterminate result due to crash or connection loss<br />
}}<br />
<br />
{{TodoItem<br />
|Report xlog position in commit message<br />
|Help enable client-side failover by providing a token clients can use to see if a commit has replayed to replicas yet<br />
* http://www.postgresql.org/message-id/53E2D346.9030806@2ndquadrant.com<br />
}}<br />
<br />
{{TodoItem<br />
|Changes to make cancellations more reliable and more secure<br />
* http://www.postgresql.org/message-id/CADT4RqAUd7wYYsM9D7GHJnZj3J79D4W%3Dved2kqM5mVt5cuGHgg@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Clarify semantics of statement_timeout in extended query protocol<br />
|Batched and pipelined queries have unexpected behaviour with statement_timeout. Client needs to be able to specify statement boundary with protocol message.<br />
* https://www.postgresql.org/message-id/20160528.220442.1489791680347556026.t-ishii@sraoss.co.jp<br />
}}<br />
<br />
{{TodoItem<br />
|Create a more efficient way to handle out-of-line parameters<br />
* [https://www.postgresql.org/message-id/12500.1470002232%40sss.pgh.pa.us Re: Slowness of extended protocol]<br />
}}<br />
<br />
{{TodoItem<br />
|Separate transaction delineation from protocol error recovery (in v3 both are managed via the same Sync message)<br />
* https://www.postgresql.org/message-id/CADT4RqDdo9EcFbxwB_YO2H3BVZ0t-1qqZ%3D%2B%2BdVMnYaN6BpyUGQ%40mail.gmail.com<br />
* https://www.postgresql.org/message-id/CAMsr%2BYEgnJ8ZAWPLx5%3DBCbYYq9SNTdwbwvUcb7V-vYm5d5uhbQ%40mail.gmail.com<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Documentation ==<br />
<br />
{{TodoItem<br />
|Provide a manpage for postgresql.conf<br />
* {{messageLink|20080819194311.GH4428@alvh.no-ip.org|A smaller default postgresql.conf}}<br />
* {{messageLink|200808211910.37524.peter_e@gmx.net|A smaller default postgresql.conf}}<br />
}}<br />
<br />
{{TodoItem<br />
|Document support for N<nowiki>' '</nowiki> national character string literals, if it matches the SQL standard<br />
* http://archives.postgresql.org/message-id/1275895438.1849.1.camel@fsopti579.F-Secure.com<br />
}}<br />
<br />
== Exotic Features ==<br />
<br />
{{TodoItem<br />
|Add pre-parsing phase that converts non-ISO syntax to supported syntax<br />
|This could allow SQL written for other databases to run without modification.}}<br />
<br />
{{TodoItem<br />
|Allow plug-in modules to emulate features from other databases}}<br />
<br />
{{TodoItem<br />
|Add features of Oracle-style packages<br />
|A package would be a schema with session-local variables, public/private functions, and initialization functions. It is also possible to implement these capabilities in any schema and not use a separate &quot;packages&quot; syntax at all.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php <nowiki>proposal for PL packages for 8.3.</nowiki>]<br />
* [http://www.postgresql.org/message-id/CAFj8pRD4OAXp2zp7dBRg5eo6X3rtT5MHTMVRN1e1kdK8xE6E4g@mail.gmail.com proposal: schema PL session variables]<br />
* [https://www.postgresql.org/message-id/CAFj8pRCfdTLeJbTSbAFOwhuS-aWaJ61w59XwKLcVYQFAVwfVCw%40mail.gmail.com proposal: session server side variables]<br />
* [https://www.postgresql.org/message-id/81060c9d-73df-2266-8857-d584164bb699%40commandprompt.com Packages: Again]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider allowing control of upper/lower case folding of unquoted identifiers<br />
* [http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php <nowiki>Bringing PostgreSQL torwards the standard regarding case folding</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php <nowiki>Re: [SQL] Case Preservation disregarding case sensitivity?</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php <nowiki>TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php <nowiki>Identifier case folding notes</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php <nowiki>Identifier case folding notes</nowiki>]<br />
* [https://www.postgresql.org/message-id/ACF85C502E55A143AB9F4ECFE960660A17282D@mailserver2.local.mstarlabs.com Cluster wide option to control symbol case folding]<br />
}}<br />
<br />
{{TodoItem<br />
|Add autonomous transactions<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php <nowiki>autonomous transactions</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Give query progress indication<br />
* [[Query progress indication]]<br />
}}<br />
<br />
{{TodoItem<br />
|Rethink our type system<br />
* [[Rethinking datatypes]]<br />
}}<br />
<br />
== Features We Do ''Not'' Want ==<br />
<br />
The following features have been discussed ad nauseum on the PostgreSQL mailing lists and the consensus has been that the project is not interested in them. As such, if you are going to bring them up as potential features, you will want to be familiar with all of the arguments against these features which have been previously made over the years. If you decide to work on such features anyway, you should be aware that you face a higher-than-normal barrier to get the Project to accept them.<br />
<br />
{{TodoItem<br />
|Rewrite the code in a different language (not wanted)<br />
* https://www.postgresql.org/message-id/CAASwCXdQUiuUnhycdRvrUmHuzk5PsaGxr54U4t34teQjcjb%3DAQ%40mail.gmail.com<br />
* https://www.postgresql.org/message-id/CANvSX4wsVhDrqy4Ku81wHs%2D%2DaViYthJ_G5G-2VeZ%3DJboEE9TNQ%40mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|All backends running as threads in a single process (not wanted)<br />
|This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve. Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features. Moving to a threaded engine would also require halting all other work on PostgreSQL for one to two years.<br />
* [https://www.postgresql.org/message-id/942824238.20160712165757@bitec.ru One process per session lack of sharing]<br />
}}<br />
<br />
{{TodoItem<br />
|"Oracle-style" optimizer hints (not wanted)<br />
|Optimizer hints, as implemented in Oracle and other RDBMSes, are used to work around problems in the optimizer and introduce upgrade and maintenance issues. We would rather have such problems reported and fixed. We have discussed a more sophisticated system of per-class cost adjustment instead, but a specification remains to be developed. See [[OptimizerHintsDiscussion|Optimizer Hints Discussion]] for further information.}}<br />
<br />
{{TodoItem<br />
|Embedded server (not wanted)<br />
|While PostgreSQL clients runs fine in limited-resource environments, the server requires multiple processes and a stable pool of resources to run reliably and efficiently. Stripping down the PostgreSQL server to run in the same process address space as the client application would add too much complexity and failure cases. Besides, there are several very mature embedded SQL databases already available.}}<br />
<br />
{{TodoItem<br />
|Obfuscated function source code (not wanted)<br />
|Obfuscating function source code has minimal protective benefits because anyone with super-user access can find a way to view the code. At the same time, it would greatly complicate backups and other administrative tasks. To prevent non-super-users from viewing function source code, remove SELECT permission on pg_proc.<br />
* [http://archives.postgresql.org/pgsql-general/2008-09/msg00668.php <nowiki>Obfuscated stored procedures (was Re: Oracle and Postgresql)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Indeterminate behavior for the GROUP BY clause (not wanted)<br />
|At least one other database product allows specification of a subset of the result columns which GROUP BY would need to be able to provide predictable results; the server is free to return any value from the group. This is not viewed as a desirable feature. PostgreSQL 9.1 allows result columns that are not referenced by GROUP BY if a primary key for the same table is referenced in GROUP BY.<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-03/msg00297.php <nowiki>Re: SQL compatibility reminder: MySQL vs PostgreSQL</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|On-disk bitmap indexes (not wanted)<br />
|The rigidity of on-disk bitmap indexes, and the existence of GIN and in-memory bitmaps make this undesirable.<br />
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php <nowiki>Re: Bitmap index AM</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php <nowiki>Bitmap index thoughts</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php <nowiki>Stream bitmaps</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php <nowiki>Re: Bitmapscan changes - Requesting further feedback</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php <nowiki>Updated bitmap index patch</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php <nowiki>Reviewing new index types (was Re: [PATCHES] Updated bitmap indexpatch)</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01023.php <nowiki>Bitmap Indexes: request for feedback</nowiki>]<br />
* [http://archives.postgresql.org/message-id/800923.27831.qm@web29010.mail.ird.yahoo.com <nowiki>bitmap indexes - performance</nowiki>]<br />
* [http://www.postgresql.org/message-id/20130914181424.GA24448@toroid.org <nowiki>[PATCH] bitmap indexes</nowiki>]<br />
}}<br />
<br />
[[Category:Todo]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=FOSDEM/PGDay_2023_Developer_Meeting&diff=37522FOSDEM/PGDay 2023 Developer Meeting2023-02-07T22:25:11Z<p>Davidrowley: Replace Thomas with Tomas</p>
<hr />
<div>== FOSDEM 2023 Developer Meeting schedule by Time and Room ==<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Madrid<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 8:30-9:00<br />
|Welcome and Introductions<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 9:00-9:30<br />
|Improving index performance<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 9:30-10:00<br />
|Extensions & SMGR<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 10:00<br />
|Coffee<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 10:00-10:30<br />
|TAMs<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 10:30-11:00<br />
|XLog Format<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 11:00-11:30<br />
|Page Format<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 11:30-12:00<br />
|ResourceOwner Patch<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 12:00-12:30<br />
|ICU / Collations<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 12:30-13:00<br />
|Lunch<br />
<br />
|- style="background-color:lightgray;"<br />
|Tue 13:00-13:30<br />
|Improving wait events<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 13:30-14:00<br />
|Extensions & Stats<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 14:00<br />
|Coffee<br />
<br />
|- style="background-color:lightgray;"<br />
|Wed 14:00-17:00<br />
|v16 Patch Triage<br />
|}<br />
<br />
<br />
== Notes/Minutes ==<br />
<br />
=== Improving index performance ===<br />
<br />
Matthias has been working on improving index performance. Concerned about interest in improvement in B-Tree performance. Improve how we use the data on the page. Multiple columns we can sometimes skip the first few columns because they're likely to be equal. Would like to know if it's worth it to continue on that. Responses mainly from Peter G but not others and want to gauge interest. nbtree performance improvements, specialization on .. PGConf.Eu presentation which showed improvements still possible. Sort on index key ranges with min/max index instead of whole table sort. Faster top-N sort with BRIN. Tomas working on this.<br />
<br />
Andres - are these changes attacking the most common performance issues. BTree index performance is more in CPU overhead and less in how data is stored. Builds search keys from scratch and code seems designed for cache misses. Very basic optimizations that we should be doing to improve btree performance. Benefits from how data is stored is constrained by these other issues. We don't keep the block numbers anywhere useful so we have to get-block-number all the time and that is horrible for performance due to cache misses and cache lines.<br />
<br />
Matthias- I see your point, not something I had been looking at when I started working on it.<br />
<br />
Heikki- These are orthoganal changes<br />
<br />
Andres- Don't find the structural changes as interesting due to the CPU overhead, et al<br />
<br />
Matthias- I get that these changes could be done too and would compliment each other.<br />
<br />
Peter E- Initial patches didn't have good performance numbers or clear improvements and so wasn't clear how it was going to help. Selling the patch better would help get interest.<br />
<br />
Matthias- Lots of people have SSDs and fast storage and on single keys and in those cases these patches don't really help. Much of the work is making sure that these cases don't degrade while improving the multi-key cases.<br />
<br />
Heikki- Are these useful on their own?<br />
<br />
Matthias- Yes, the patches are useful on their own. Improvement in multi-key indexes while not degrading the default case. Makes it complicated.<br />
<br />
Jeff- What was your motivation to work on this?<br />
<br />
Matthias- We had a really large index across three columns which was really slow at a prior company to do lookups. We couldn't use btree deduplication for $reasons. Was thinking "why is this so slow?" and was largely because the attribute had to be compared for every column but we don't need to do that in every case because we know that the first columns are the same. Improvements seen 10-20% on index insertion and lookup.<br />
<br />
Jeff- That sounds pretty compelling but thread was hard to guess from what was in the patch what the improvements were.<br />
<br />
Matthias- 31 text column index which go into compare path plus one uuid patch which gave 200-400% improvements because we can skip the earlier columns.<br />
<br />
Heikki- You can construct cases which can show the improvement.<br />
<br />
Jeff- Constructed cases aren't very compelling but actual use cases which show strong 10-20% improvement are a much better way to sell the patch.<br />
<br />
Jeff- Which collation provider was being used?<br />
<br />
Matthias- The non-default collation because it's more expensive which helps demonstrate the improvement, but even with the default collation there were improvements.<br />
<br />
Andres & Matthias discussion about better approaches to scanning and constants.<br />
<br />
Matthias- In PG14, Peter G committed some changes to btree where tries to delete items on the page when it does a split to avoid a split. May be able to implement the same for the other index types which could improve performance of those other index types. Don't have time to work on it currently but someone else could work on.<br />
<br />
Andres- Index insertion path improvements by doing a pre-sort which can help a lot. No reason to not do a pre-sort when doing batch inserts. Not able to do it in every case due to triggers and such but in many cases it could be done and would help performance.<br />
<br />
Mark Dilger- What is causing the improvement?<br />
<br />
Andres- Just try it and you'll see the improvement.<br />
<br />
Heikki- The table will also immediately be sorted and so you don't have to CLUSTER. If index could keep track of recent inserts then it could order them and insert them.<br />
<br />
Andres- Like GIN fast insert.<br />
<br />
Heikki- Yes, but better. Could be done pretty simply in the index access method..<br />
<br />
Andres- Not sure doing it in index access method is best as it could be the same code copied a bunch of times, better to do it higher up..<br />
<br />
Heikki- Yeah, better to have a batch insert access method function<br />
<br />
Bruce- Folks are frustrated and sometimes the people working on things may feel like a 'lone ranger'. Is there anything we can do to try to avoid that? Particularly with the more specialized stuff, the farther down you go, the more peoples eyes may glaze over. We encourage people to take on these hard problems but it may seem like people don't care about it, but people really do care about it, a lot of people are interested and don't feel that people don't care. Anything we can do to try to improve on that?<br />
<br />
Heikki- Some folks have said that working on PG can have an impact on mental health due to frustration of working on PG.<br />
<br />
Bruce- Not a topic here but feels like something we could work on improving.<br />
<br />
Matthias- The commitfest topics and patch names aren't very descriptive of what expertise is needed to review the patches. Maybe could add "area" such as "indexes" or "access methods" or such to the commitfest system.<br />
<br />
Peter E- How are those defined, could we change them?<br />
<br />
Magnus- Might be able to be modified by CF Admin or superuser.<br />
<br />
Peter E- Always wished for adding categories because lots of patches end up under Misc.<br />
<br />
Matthias- I don't mind the topic part but also need the distinction of what part of the code is being modified and what expertise is needed.<br />
<br />
Peter E- How would you do it? Maybe tags?<br />
<br />
Matthias- Maybe general areas would help.<br />
<br />
Andres- Doubt the commitfest app is where the issue is here.<br />
<br />
Matthias- Maybe could make it easier to find patches.<br />
<br />
Peter E- Have to sell your patches.<br />
<br />
Heikki- Problem of contributors getting frustrated and going away. People post patches they feel are brilliant but then they don't get any feedback on it. Or people put time and effort and then don't hear anything for months and then the result is that we don't want it.<br />
<br />
Mark- I'm also working on index improvement but going at it in a different direction, changing heap code and not index code to make improvements and so it isn't clear if there's an overlap there or not.<br />
<br />
=== Extensions & SMGR ===<br />
<br />
Matthias- At company we would like to be an extension and not a fork but we bind deeply into the SMGR APIs. How well would PG be accepting of SMGR available to external users to avoid having to be a fork.<br />
<br />
Peter E- Way back to 6.0 we had this<br />
<br />
Matthias- We ressurected that<br />
<br />
Peter E- Also looked into this and just have to come up with a way to do it but everything is today hard-coded. Maybe like tablespace with a local override or something.<br />
<br />
Andres- Has to work at all times including in an inconsistent state because we use it during recovery and therefore can't look at catalogs, et al. Worried about code complexity for core PG where PG is just making things easier for forks or other projects but making it too complicated for core without any benefit.<br />
<br />
Heikki- Lets imagine opening up smgr read and smgr write<br />
<br />
Peter E- That or md.c functions?<br />
<br />
Heikki- Does it make a difference?<br />
<br />
Andres= Could use compiler flags to override that using linker magic.<br />
<br />
Mark- Change the whole cluster?<br />
<br />
Heikki- Yes, across the whole cluster.<br />
<br />
Mark- Can't really do that from an extension then because you need to init the DB and load the extension first.<br />
<br />
Andres- You would only be able to do this at initdb if for the whole cluster<br />
<br />
Heikki- Also use md.c for temporary files and things instead too.<br />
<br />
Andres- How are you handling figuring out when to use what?<br />
<br />
Heikki- Hack in smgr.c to pass in a flag to indicate the kind of table<br />
<br />
Matthias- Passed in the type of relation to then control how we access the files<br />
<br />
Heikki- Or we could have it a level above to specify the functions to access<br />
<br />
Mark- This is for storage as a service, so you could just swap out the whole storage manager<br />
<br />
Matthias- We are modifying the functions that call into the storage manager to call our hooks so we don't use the smgr storage structs<br />
<br />
Heikki- We have hacked to pass in what kind of table it is<br />
<br />
Jeff- Could we do it at tablespace level instead<br />
<br />
Matthias- We don't currently force all temporary tables to a particular place<br />
<br />
Heikki- May have an issue with what Andres said about being able to recover before being able to do catalog lookups<br />
<br />
Andres- yeah, not sure that tablespace makes sense for this.<br />
<br />
Heikki- Other things that you could do, maybe encryption or compression, not sure if that would work. Another cool thing would be to do something with backup to fetch the data on-demand from like pgbackrest.<br />
<br />
Peter E- Maybe instead of storing on disk, store out in the cloud somewhere. Not easy to play with the changes since there isn't a good API<br />
<br />
Jeff- What about the non-smgr file access that's going on.<br />
<br />
Heikki- All of the SLRUs, work around that by not doing things with those and those are still stored locally. Would be cool if they also went through smgr API.<br />
<br />
Mark- How would that work? Multiple nodes connected..<br />
<br />
Heikki- When you start up PG, you need a base backup to start from with control file and other little things and the SLRUs. Just restore those as-is. SLRUs are pretty small so that is ok. All of the relations are stored in the cloud and get accessed through the SMGR API. Only one writer to handle the sync issues.<br />
<br />
Mark- This isn't multi-master?<br />
<br />
Heikki- No, this isn't multi-master. All the table and index accesses go through the SMGR API. There are some places where we have to modify the code for index builds. One thing causing us trouble is some writes through SMGR are not going to be WAL logged. GIST index builds the index first and then WAL logs everything after. smgr write for us is a no-op and then on read we reconstruct from WAL. Maybe add assertion that everything is WAL logged to make sure all modified pages are actually WAL logged.<br />
<br />
Andres- Hint bits?<br />
<br />
Heikki- Think we just throw those changes away now but we could possibly do better.<br />
<br />
Andres- Sounds like you need to do the work to propose a patch and then we can see if the complexity is really bad or not.<br />
<br />
Matthias- There is not zero external interest in this.<br />
<br />
Mark- Sounds interesting and we would be interested in seeing a patch for it.<br />
<br />
Heikki- One thing that bothers me about md.c and smgr.c- the way they treat the relation forks is kinda ugly. md.c needs to know about all the forks and there's an array for the segments and forks and segments on forks. Would be better if md.c didn't have to deal with that and instead dealt with one fork at a time. smgr.c could maybe deal with forks.<br />
<br />
Andres- That doesn't seem quite right. You would have to somehow group the data together. Looked at that problem at one point and maybe we could have completely different relfilenodes for forks instead and have one fork for main relation and a different relfilenode for the VM would make things simpler.<br />
<br />
Peter E- Set of forks are hard-coded in a lot of places.<br />
<br />
Heikki- Larger relfilenode we could do that<br />
<br />
Matthias- 56-bit relfilenode would allow us to have room for that<br />
<br />
Peter E- What about other kinds of forks that other kinds of storage might want to add, maybe as an extension or maybe not, not everything may need the free space map, etc.<br />
<br />
Heikki- Working on column-store before would like to have a separate relation fork or something like that for each column.<br />
<br />
Jeff- Might be harder to do that but at least having more than one ... there's a difference between allowing a few extra forks vs. allowing potentially hundreds.<br />
<br />
Andres- But what about init forks which are weird magic, may have to come up with something different for that. Init forks maybe a separate directory then you wouldn't have to iterate over everything and could work and would allow to have initial data.<br />
<br />
Peter E- forks are used by different parts of the system such as init forks being hooked into the crash recovery system<br />
<br />
Heikki- init fork change would be good to do independently.<br />
<br />
Andres- had a patch to allow you to associate a given relation with multiple relfilenodes in pg_class but didn't quite get it all done<br />
<br />
=== TAMs ===<br />
<br />
Mark- As Andres mentioned, not want to only accept things into core that are for forks. Chicken and egg when it comes to TAMs though. More baked into core that we have heaps, lots of code doesn't talk about tables but they talk about heaps. Lots of assumptions. Mainly interested from the group in trying to address the chicken and egg issue when it comes to TAMs or to see what the better way to go about it is. Company worked on zHeap for a while and was excited but not sure if it's ever coming back. Tendancy to think of new TAMs as where devs go into the wilderness to pass away. Two TAMs developed and released to solve specific performance problems in production. Working on new TAMs with different on-disk formats. Anyone else working on TAMs is likely to want this too. How to share these improvements in core for these other TAMs. There are some functions that call the heap functions directly still and don't go through the TAMs. If we put a different TAM out but when these differences exist and something accesses directly through heap functions then you end up with bugs. Created the Contrary AM to store everything differently on disk intentionally. If you use Contrary AM, you can find where functions which access the heap directly will explode and break. Happy to contribute that back but not just that, could write a TAM which will provide better performance but which aren't heap. Should we have a contrib module to make sure that the TAMs don't get broken.<br />
<br />
Heikki- TAMs should be how everything access, but those are bugs if they access the heap directly and should be fixed.<br />
<br />
Mark- Extensions exist out there or forks which access the heap directly and that's where the bugs are.<br />
<br />
Andres- For a beginscan could check that what was given is actually a heap and so there should be a catch happening but if we don't have that then we could add that.<br />
<br />
Jeff- Could we add preprocessor magic to check if someone is calling the heap functions but throw an error if they are being called from not through a TAM that could maybe throw an error during compile time maybe.<br />
<br />
Andres- Not sure we could do that and that might cause more harm than it would help.<br />
<br />
Heikki- What extensions are doing that?<br />
<br />
Peter E- pglogical is doing that.<br />
<br />
Heikki- Why does it do that?<br />
<br />
Peter E- Fixable but could build more scaffolding to avoid new extensions doing that.<br />
<br />
Alvaro- How much is there between heap and the Contrary AM?<br />
<br />
Mark- When you have a loadable module you expect in minor upgrade for those modules to continue to work, don't expect that the module is updated at the same time as the core code. If you copy the heap code and make it pile and add it as a contrib module as a TAM but identical to heap. If you upgrade from 15.0 to 15.1, it should be fine, but you don't know for sure and the community may change the heap code in a way that changes things that aren't compatible. Maybe we could have something in contrib which runs in the buildfarm to detect such changes.<br />
<br />
Andres- What minor version changes has this happened in? We've only had like three of these recently, just those?<br />
<br />
Mark- Yes, just those.<br />
<br />
Heikki- Is this just for contrarian AM or are there real cases where the heap changes in minor versions have caused issues?<br />
<br />
Peter E- May only happen once a year or once every three years but when it does happen it's very tramatizing...<br />
<br />
Mark- We have several customers with heap performance problems and they continue to ask for fixes. Index bloat due to holding open a transaction and lots of updates, lots of tuple versions across pages and lots of index bloat. Make a solution to that problem and give it to the customer, you're very nervous that this new AM won't survive minor version updates. Would like a better guarantee that this won't be an issue in minor version upgrades.<br />
<br />
Andres- Don't recall a case in core where we have had an issue with this and sounds like isn't a core issue really but is an issue in extension. Not obvious how we could test for this in core because it's an issue in something external. Maybe something that tests for signatures.<br />
<br />
Mark- Does anyone else that wants in TAM... want to spend maybe a year working on a new TAM to allow push-down and contribute to the community. Others interested in predicate push-down stuff?<br />
<br />
Jeff- Yes, interested in that.<br />
<br />
Andres- Heap could be interested in this too<br />
<br />
Heikki- A few things left in core that assume there is something like heap. ANALYZE assumes you have blocks. Would be nice if there was a function in the TAM API. Was expecting that to be brought up.<br />
<br />
Peter E- Not really going into fully different things with this- things are still blocks.<br />
<br />
Heikki- bitmap heap also assumes blocks still<br />
<br />
Mark- If you take a bit of space to say what kind of page it is then you could have your scan skip blocks that aren't interested in that. Don't need an API change for that really. Will TABLESAMPLE land on the wrong kind of block maybe, is that an issue?<br />
<br />
Heikki- That seems like it may be an issue, yes.<br />
<br />
Andres- Some pretty easy API changes for bitmap heap scans but after that you're going to have to have something that's block shaped.<br />
<br />
Heikki- With bitmap heap scan, the problem is that it degrades and becomes lossy and you have to scan all tuples on a particular block.<br />
<br />
Matthias- Becomes lossy quite quickly, could imagine TAM that has many many line pointers per page / TIDs, so bitmap heap scans likely to always be lossy which could be pretty annoying.<br />
<br />
Andres- Someone working on patch to use radix for vacuum and that could maybe be used for bitmap heap scans, not a small change.<br />
<br />
Matthias- Not sure if happy with this part of TAMs, but also a patch to do batch inserts for things like insert into select<br />
<br />
Mark- Would be fantastic. Some of the code about assuming the number of tuples per page doesn't really work because I don't want to store the header over and over again, end up sorting the data as it comes in to improve performance and improve compression.<br />
<br />
Andres- Is that a question of TAM or executor code?<br />
<br />
Matthias- Both, right now when we batch insert we only do in copy, only happens with full batch inserts. Patch proposed to make possible to do batch insert in TAM and allow to buffer for later insertion and could use that to reduce WAL size and improve performance of compression. Old patch that hasn't been updated in quite some time, about a year ago. New TAM for multi and single inserts is the patch.<br />
<br />
Jeff- A lot more infrastructure could be provided for conditional push=down around things like parameterization. Ideally a TAM would advertise the columns that would be interesting for parameterization and then the planner could generate and cost those paths. That could be a combinatorial problem explosion, the planner would need to handle pruning that. Would be useful infrastructure. Can be done with custom plans now but think that a lot of TAMs would want this and therefore would be good common infrastructure for that.<br />
<br />
Heikki- Does that predicate push-down make sense...<br />
<br />
Jeff- Rather than do the predicate push down, let it return some other structure to the executor and let is handle it there? I think that's a good point but it seems like the horizon for actually making that fully generic is pretty far out there. As an extension author, just trying to get something running, you'd have to do that with a custom scan.. You want to do some simple predicate push-down you have to invent a whole bunch of things in a custom scan and that's a pretty long path when you may have a simple structure which would let you rule out a bunch of rows that aren't interesting to scan very quickly. Instead, being able to say parameterize me and provide that path to the executor would be simpler/faster to have.<br />
<br />
Andres- Possible issue with taking out exclusive locks in part of this but we could probably work around that to make it better and possibly provide a substantial speedup.<br />
<br />
Jeff- If we rearrange some of this, we may be able to rework how index parameterization is done. Don't have a lot of details there but essentially if you have a TAM with predicate push-down, looks a lot like a nested loop index scan from the point of view of the planner.<br />
<br />
Heikki- Could we use the exact same scankey infra for TAM that we do for index scans..?<br />
<br />
Andres- Today it's different<br />
<br />
Heikki- but you'd want it to be the same<br />
<br />
Jeff- Don't have a way to do that today<br />
<br />
Heikki- Have a heapscan key today in the TAM but we don't really use it today.<br />
<br />
Mark- If you ask for all rows where ID=5, you go to the index to get it, you don't really ask that of the TAM. There's an opportunity there for improvement if we also pass that through the TAM to eliminate things that the TAM has to do.<br />
<br />
Jeff- Thinking of the TAM to do less, would have to write a lot of custom scan code but could be done with custom scan node and TAM today, all doable but it should be common infra.<br />
<br />
=== XLog Format ===<br />
<br />
Matthias- Complaint- it's large. We have 44 bytes to just change 1 page. 24 bytes are xlog header, remaining bytes used in determining the actual page and related overhead. Don't think we should have that much overhead for changing a page. There are changes we could make to reduce that overhead if we are willing to make those changes. A few discussed before on the lists. Looking at what changes we actually can make, for instance- transaction IDs are included but few cases where we actually need transaction ID. Indexes are not aware of transactions and don't use transactions, maybe we can eliminate transaction IDs from index updates. Length of record currently uses 4 bytes but records themselves may need less than a byte to store that, and should be able to reuse the rest. Potential problem there is that the decoding may become fairly expensive.<br />
<br />
Peter E- Send a patch!<br />
<br />
Matthias- Would have but have run into issues with decoding/unpacking of struct. When record is split across pages because it's too large or just didn't fit, right now we copy the whole record into a separate buffer that is allocated and then we checksum and then we decode it. For large records we have overhead of reading the record twice. Very expensive. Should be able to do decoding and checksumming in one pass, many opportunities to figure out that the record doesn't fit and the checksum at the end is good to validate the record. Don't need to checksum the full record before we start decoding.<br />
<br />
Heikki- All comes down to performance, send a patch and benchmark it. More principaled questions- Do we need to store the XID on every change for $reasons like debugging perhaps?<br />
<br />
Alvaro- Used by pg_rewind?<br />
<br />
Heikki- No<br />
<br />
Matthias- Not every xlog record gets generated in backends that have local transaction ID<br />
<br />
Andres- today we have generic handling of it but changing that means we need to make sure we copy transaction ID to everywhere that needs it<br />
<br />
Heikki- Would it be ok to compress the WAL itself? Do some kind of fields to the page header for the relfilenode so that it is only stored once instead of every time, or maybe reference previous WAL record, to avoid having to save the relfilenode over and over.<br />
<br />
Andres- Locking for that would be awful and adding intra-record stuff would be bad. Maybe reference the page header for multiple records within a page and could do that opportunistically maybe<br />
<br />
Matthias- We build the record before we know where the record is going to go<br />
<br />
Andres- already able to modify the checksum and we could change where it goes<br />
<br />
Heikki- This could change the size though is very different from calculating the CRC because impacts records after. Comes down to the xlog insert path as that has to be highly concurrent, assuming we could make it work we could do it. Kind of wasteful that we store CRC, et al, on every record but then we flush the records in larger buffer, maybe we should have a frame or page that contains multiple records.<br />
<br />
Peter E- but then you still have to go back, concerned about the size or..?<br />
<br />
Heikki- People concerned about size yes, though mostly about FPIs, but still<br />
<br />
Peter E- Decoding speed vs insert speed and size<br />
<br />
Andres- Record length variable width maybe... pg_waldump --stat was pretty reasonable on a big workload with variable record length, could optimize that further. If the data can be organized to make decoding cheap then could help but we have such low-hanging fruit like we store 4-byte integers where 3-bytes could be used, but just generally reducing alignment losses, et al. WAL was more than 60% zeros or something like this.<br />
<br />
Matthias- there are some alignment places where there are zeros..<br />
<br />
Heikki- We could possibly just compress the WAL when we write it.<br />
<br />
Matthias- Compress record or stream?<br />
<br />
Heikki- Compress the whole stream.<br />
<br />
Andres- Constantly end up flushing the last page multiple times which is pretty bad for OLTP workloads<br />
<br />
Heikki- Have to have an append-only compression algorithm<br />
<br />
Peter E- If you do that then you can only compress the flush size and that may not make sense<br />
<br />
Heikki- Not as good as compressing the file afterwards but still could be better<br />
<br />
Alvaro- Proposing using compression to avoid improving the base layer of how we write WAL<br />
<br />
Heikki- Can be an effecieint way to address it<br />
<br />
Andres- One thing reminded me of for AIO, for network storage and slow storage, partially filled pages can't be overwritten concurrently and that becomes an issue. Have multiple IOs for different pages concurrently but can't do that for last page in WAL. Got performance improvements by using new pages constantly to parallelize it but that blows the WAL up really big so isn't good but does improve performance. Don't really see how to improve with the way partial pages happen. Reduce the block size to 4k instead of 8k as 8k doesn't give us any benefits and makes it much more common to have partial pages and on the filesystem typically have 512 or 4k granularity and so you just add overhead with 8k bytes and read/modify/write cycles.<br />
<br />
Heikki- Would be great to get rid of the WAL header entirely..<br />
<br />
Peter E- Only drawback is that you have more records split<br />
<br />
Matthias- Still need the segment header but that's ok<br />
<br />
Heikki- Think you're replying to me and just talking about the size change and yeah<br />
<br />
Andres- if you start to write WAL that's not page-aligned then performance suffers really badly.<br />
<br />
Heikki- Makes the decoding and encoding of WAL more complicated as you have to keep track of those headers<br />
<br />
Andres- You can't read as randomly from the WAL because you don't know where things start and end, but wouldn't know that without the header. Two-phase commit stuff ...<br />
<br />
Heikki- Reducing the page size and just flush have a page rather than full page and get same benefit?<br />
<br />
Tomas- You will still modify the page multiple times and dirtied the page multiple times<br />
<br />
Heikki- Keep xlog size at 8k but at xlog flush then flush at 4k<br />
<br />
Peter E- Then you introduce a different idea of what a page is<br />
<br />
Andres- Don't see a real advantage to having 8k page size, doesn't seem advantagous.<br />
<br />
Heikki- You're saying it's useful to have 8k page size WAL?<br />
<br />
Andres- No, I don't see it being useful at all<br />
<br />
Heikki- As far as I'm concerned maybe we should have 32k or 16MB page size instead of having it be smaller to reduce page header overhead<br />
<br />
Andres- Able to determine end of WAL more easily<br />
<br />
Matthias- When we recover to a broken record, usually we expect it to be because a split page write and that's where we know the WAL ends. Kind of important because as was mentioned in 56bit relfilenodes, we might write WAL all the way back to a prior flush<br />
<br />
Andres- Would be pretty bad to have to reflush a 1GB segment<br />
<br />
Matthias- Right now the page header the wrong LSN will be seen<br />
<br />
Heikki- If it's not a recycled earlier segment but is a new segment...<br />
<br />
Stephen- Comments about larger field for AES GCM auth tag.<br />
<br />
=== Page Format ===<br />
<br />
Matthias- Right now we have normal page format which is used and available for various AMs. There are ideas about TDE which want to change the format to reserve some space for auth tag or other things like extended checksums. I think that space should not be at the exact end of the page while we are in memory, don't care about it when on disk, but in-memory that is prime real-estate.<br />
<br />
Discussion about page changes to store extended checksums or 64bit XID or auth tag.<br />
<br />
Tomas- 4k pages can greatly improve performance in OLTP workloads<br />
<br />
Andres- Case where low-cache hit ratio, shared buffers isn't enough to fit things<br />
<br />
Tomas- yes, in cases where shared buffers isn't large enough<br />
<br />
Andres- Might be more a factor of line pointers distance to the tuples<br />
<br />
Matthias- Shouldn't be an issue if huge pages are being used<br />
<br />
Andres- If huge pages used then yes but with prefetching there's heuristics that may not work if it's too far<br />
<br />
Tomas- When it fits into shared buffers it doesn't seem to make meaningful difference.<br />
<br />
Andres- That makes sense and is mainly write volume and not specific to SSDs really<br />
<br />
Tomas- SSDs have erase blocks but they're split into pages but the faster you write the faster you write into erase blocks, generate more work. Definitely it's a combination of multiple parameters.<br />
<br />
Andres- Dirty write-back with SSDs where they go back and write out blocks in a row to avoid having to make the system read in a page and then write it out can make a huge difference.<br />
<br />
Peter E- How can we get more people to use checksums?<br />
<br />
Andres- Right now there's a big performance hit from using checksums in some cases because WAL logging of hint bits causing a performance hit.<br />
<br />
Matthias- Idea to reduce hint bit writes in the WAL from changes with checksums enabled. There is no split page potential? Even if there is a torn page, you still redo the record.<br />
<br />
Heikki- Partial full-page?<br />
<br />
Matthias- Yes..<br />
<br />
Andres- Typically is going to be a full-page change anyway so doesn't really help<br />
<br />
Matthias- For freezing which is a common case, changing a lot of things on the page from visible to frozen, just changes bits, the meaningful bits aren't being changed<br />
<br />
Heikki- Point is when you write the WAL record, you'd have to say modify this bit or that bit<br />
<br />
Matthias- organization of the page doesn't change<br />
<br />
Matt- Who is we<br />
<br />
Matthias- the information on the page, while freezing we aren't changing the data of the page, whatever torn bytes there are going to be aren't changing the bytes that are meaningful. Reason for torn page protection is that the line pointer array may change and the tuples may be getting changed but if we don't change where the tuples are then a torn page shouldn't be an issue<br />
<br />
Andres- not sure that that's true, maybe for hint bits but not for freezing<br />
<br />
Matthias- even for freezing, it's only sets of bits that are being updated, fairly certain that we can improve on this. Think there are places where maybe we don't need to push out a full page image.<br />
<br />
Andres- Don't think it's enough, still need to do a full page write or need a second LSN<br />
<br />
Matthias- We do have space in the page header bits, only have a couple of bits used<br />
<br />
Andres- As soon as you have checksums this is all gone<br />
<br />
Heikki- This is for checksums too, you do a partial full-page write that's not as large, but seems hard to pull off<br />
<br />
Matthias- Yes, extremely difficult but not impossible.<br />
<br />
Heikki- What if we stop writing those hint bits?<br />
<br />
Andres- the performance hit is very large if you just don't write them at all<br />
<br />
Peter E- Vacuum-ish kind of process that does it sometimes still<br />
<br />
Andres- the SLRU lookups kill you immediately in terms of performance<br />
<br />
Jeff- Maybe a tiny cache that would help?<br />
<br />
Andres- Maybe could win a lot with a tiny hash table cache. Could cache xid to parent to win a lot to help with subtrans too.<br />
<br />
Heikki- Have a better SLRU system and cache but isn't going to be as good as hint bits on the tuple<br />
<br />
Bruce- Have a scratch space for a table, always have an extra dead page in the table, instead of writing page 10, you write it into the dead space and have that space in the table. The reason we have trouble is because we can't go back to the old version of the table.<br />
<br />
Andres- Then have really hard problems with possibly returning double tuples<br />
<br />
Heikki- So whenever you write the page to disk you write to double-buffer area and it's an alternative which has downsides but is possible<br />
<br />
Andres- No need to log hint bit changes immediately and so maybe we could batch them and reduce the xlog overhead and WAL logged hint bits<br />
<br />
=== ResourceOwner Patch ===<br />
<br />
Heikki- Have patch to change the way they work internally and make them useful in extensions. Not using them currently in any extensions but for others to use if it's useful. Patch made some changes to how ResourceOwners work. Objections from Andres- with Heikki's patch resources are released in random order. May have made exception for locks.<br />
<br />
Jeff- Motivation?<br />
<br />
Heikki- pgcrypto wants to track some things in ResourceOwners, when wrote that code was very painful because couldn't use them. There's callbacks but they're really difficult to use. Hard for an extension to leverage ResourceOwners from extension. In core we have 10-15 uses for ResourceOwners and there's a lot of boiler-plate code that could be eliminated.<br />
<br />
Andres- Performance regression due to ResourceOwner getting bigger which isn't good<br />
<br />
Heikki- Hard part of patch was to keep performance good because of ResourceOwners being in critical path. Objection- released in current code is in a specific order but with the patch they get released in random order.<br />
<br />
Alvaro- Why do you care?<br />
<br />
Andres- There may be some dependencies in there and error handling needs to mark the page and has to happen before un-pinning the page during io.<br />
<br />
Alvaro- Can we create more phases<br />
<br />
Heikki- We were discussing that and maybe having a priority number or such. Not convinced that should be necessary. Would like to take a look at where that's being done. Second objection, if you need to remember a resource in a critical function you have to first call an enlarge function to reserve a slot for it. That mechanism is per resource-kind currently. Changed it so that there is just ResourceOwner enlarge instead of being per resource-kind. Difference is that if for some reason you want to reserve one buffer pin and one tuple descriptor and then you enter critical session that doesn't work because with patch can only allocate one slot. Argument is that you should keep the distance between reserving the slot and using the slot should be very small because it's already very dangerous to do this because of other calls you might end up using one by accident. New patch just reserves one slot instead of having one slot for each kind.<br />
<br />
Peter E- You could just allow reserving more than one<br />
<br />
Heikki- Yes, if you know how many you might need then you could do that. If there's any serious code between the reservation and using the slot, it's very hard to be sure.<br />
<br />
Andres- Right now we always increase by power of 2 and that's part of the reason it's hard to find off-by-one errors. Maybe change to have a counter/check to make sure that you aren't going past how many.<br />
<br />
Heikki- Maybe have a way to return what was reserved and then have the use of that pass in the value of which was reserved and throw an error if that's an issue.<br />
<br />
Andres- There should be only a few places that need more than one.<br />
<br />
Peter E- Seems solvable.<br />
<br />
Heikki- Third, for some kinds of resources you could do it differently and instead of having array and hash, keep track of resources in a linked list instead. Some resources have structs and you could use a linked list instead and that could be faster and more performant.<br />
<br />
Andres- That could also make it safer. Ran into this for AIO for WAL insert and every AIO for WAL insert had to be reserved and is in critical section and you can't allocate memory there. Not applicable to all kinds of resources but does work for some.<br />
<br />
Heikki- Maybe linked list approach could be used for basically all of these cases instead since very few cases where there aren't structs. Maybe everything could use structs?<br />
<br />
Andres- Convert most things to list then maybe could be better. Patch by Rowley to get rid of all special cases by using dlist(?).<br />
<br />
Heikki- For buffer pins could we have a local buffer struct<br />
<br />
Andres- Have to allocate it. Could do something like existing resource for hints and just use dlists or lists for everything else.<br />
<br />
Heikki- Yeah, maybe I'll try that approach.<br />
<br />
Andres- Maybe combine dlist approach with patch approach by storing allocation in dlist head so that can store header, dlist head, inside resourceowner unless it's needed and then one or two things that are needed, might be best of both worlds.<br />
<br />
Heikki- I'll play around with that if I get a chance.<br />
<br />
=== ICU / Collations ===<br />
<br />
Jeff- Issues with collations. Right city to discuss it in. One thing is PG is pretty unified and the direction users a guided in in terms of the way things should be done. Integer timestamps are better than float, et al. Should we be doing the same thing with ICU vs libc? Should we make a decision there? Are we not going to express an opinion? Of course, even if we try to not make a decision, if we leave the default as-is or change the default, that's a decision. Would we eventually like to pick one way and go with it, or stay on the fence?<br />
<br />
Peter E- Would like to move towards making ICU be used as the default.<br />
<br />
Andres- Hard dependency?<br />
<br />
Peter E- That's the problem. You can change the initdb default but it'll fail if ICU isn't compiled in. What do you do then?<br />
<br />
Tomas- What about use ICU by default if it's built-in?<br />
<br />
Peter E- Is that a good answer? Already is environment-dependent and so maybe it wouldn't be that different. Might be better as it would be a better default instead of getting it from environment.<br />
<br />
Heikki- Locale itself still depends on where it's running<br />
<br />
Peter E- Want to get rid of locales but that's kind of independent.<br />
<br />
Andres- Just make it a hard dependency?<br />
<br />
Alvaro- Are there other collation providers? Microsoft?<br />
<br />
Andres- Microsoft has ICU available but not the default for things<br />
<br />
Peter E- Collation provider concept, back of mind- there's a native API on MacOS which could have been another choice but there's no practical benefit. Doesn't seem like there's actually a bunch of different APIs, just the legacy one and the ICU one and not really interest in other.<br />
<br />
Dave- What about platforms which don't have ICU? Are there such?<br />
<br />
Andres- Don't think there really are any such. Built PG on a bunch of platforms last year and pretty much all have ICU for a long time. May not be available by default on some systems but it's available. No extra dependencies on MacOS currently to build and some appreciate that.<br />
<br />
Peter E- When on new platform sometimes it's nice to be able to git clone and build and avoid ICU because ICU is big to download and build.<br />
<br />
Heikki- Agreed that isn't great, maybe have an option to not have any collations in that case?<br />
<br />
Peter E- Question is if we want to nudge users to use that stuff.<br />
<br />
Andres- Switch the default to use if available which would at least allow devs to not have to worry about it but generally it gets used.<br />
<br />
Alvaro- Is this something we could do for 16?<br />
<br />
Peter E- What we are talking about right now as it's an easy thing to just change the default.<br />
<br />
Jeff- If we feel ICU is the right thing, we've been using it for a while and we have found some issues with it and it isn't perfect but generally my feeling is that it's a better path than libc and if the project feels that way then we should start nudging people in that direction.<br />
<br />
Joe- Not all of PG locale functionality is handled by ICU. lowercase/uppercase, C-type operations...<br />
<br />
Jeff- lowercase/uppercase do use ICU but there are some scattered cases of other things being used. strxform call when making histograms as an example maybe<br />
<br />
Peter E- Question about how to instrument these things to catch such cases would be good to figure out. tsearch uses it, on list to fix but isn't very interesting.<br />
<br />
Jeff- Those scattered places ... there are details we should work to figure out and address those cases<br />
<br />
Heikki- Even if we don't change the default, we should fix those cases anyway. Is there a reason to not use ICU?<br />
<br />
Matthias- because you're only using the C locale?<br />
<br />
Peter E- Then just say to use that?<br />
<br />
Matthias- But you could build a smaller binary with having just the C lib<br />
<br />
Heikki- Is there a performance reason to use ICU than C lib?<br />
<br />
Jeff- In my tests it's been better<br />
<br />
Joe- There was a regression introduced by the C maintainers where they made a change saying it wouldn't cause a performance issue but it actually does for multi-byte. ICU is faster if you have a lot of UTF8 multi-byte characters vs. libc. Big regression in recent versions of glibc.<br />
<br />
Jeff- If they fix that problem then in theory libc could be faster, but if they don't fix that then ICU blows away glibc.<br />
<br />
Joe- Scattered calls to glibc locale dependent functions in PG core that aren't going to ICU, concern about switching to ICU due to that<br />
<br />
Jeff- In terms of actually what the user sees, should all be handled correctly. The cases pointed out shouldn't be user-facing. A lot of those cases are with libc collation provider and not with ICU, though there were some calls that may need to be looked at. If there are user-facing issues then that's a bug that should be addressed. Assuming we can address the bugs...<br />
<br />
Matt- Independent of performance, a libc upgrade that changes sort order breaks indexes, etc. ICU would make it easier to detect/address that?<br />
<br />
Jeff- No way to change from one collation to another today and so have to keep same ICU version. But, there are potential advantages to using ICU because it's a separated library that you could manage the versioning of instead of being tied to libc.<br />
<br />
Joe- Ins't just indexes. If you have FDWs and running on machines with different versions of glibc then you'll have problems in that case too. Recent case of mysql FDW and they were having problems because a join wasn't working because the collation for mysql was different.<br />
<br />
Matt- Haven't seen a strong advantage to ICU vs glibc because that's the same problem between the two.<br />
<br />
Andres- Not really a nice way to load multiple versions to load multiple versions of ICU, but you could do that more easily with ICU.<br />
<br />
Peter E- Or you could just keep the same ICU version around generally instead of having to upgrade it, like you have to upgrade glibc due to $reasons. We could move things forward at least, not a panacea.<br />
<br />
Joe- Did a project where extracted out of glibc the locale code into a separate library to use and freeze the collation at a particular collation that way. Link PG to that library instead of the actual glibc library.<br />
<br />
Tomas- Wouldn't want to get stuck on one collation as there are improvements which happens. If there's a new glibc version, how difficult would it be to update that?<br />
<br />
Joe- Was able to test it extracting 2.17 and 2.26 and the way extracted was able to work for both. Could be extended to build a different version if needed.<br />
<br />
Tomas- How would that work? We would decide when building a major version?<br />
<br />
Joe- Think it would be something that the packagers would have to handle. Same issue with ICU.<br />
<br />
Jeff- Have working code to allow change ICU library at runtime so users could change to a new version of ICU. Could help users prevent issues with the library changing out from under them. Based on prototypes that Tomas provided earlier. Might not go into 16 but the code works. Also have prototype code which allows doing something similar for libc. Packagers could build against later version and then users would be able to choose version at initdb time. Packagers would then package up multiple versions and make them available concurrently and keep them all forever and users could then choose the one for them and keep it static.<br />
<br />
Tomas- One of the problems we have is people upgrading OS where new server has new glibc and they don't realize their indexes have gotten broken. This would be a solution to that by installing the old compat library.<br />
<br />
Joe- Have to do that before they do anything.<br />
<br />
Tomas- Is there a way to track the version and on server start check the version and refuse to start if needed.<br />
<br />
Joe- PG15 may blert a warning?<br />
<br />
Jeff- That's a different thing, colversion but that's different from the collation library version. Simplest proposal at initdb time could be to pass a flag saying which is needed and then have that track and do initialization and setting up the collation from that provider.<br />
<br />
... further discussion over lunch including about loading multiple ICU versions concurrently, tracking collation version in the catalog, allowing to build new indexes concurrently with existing, et al<br />
<br />
=== Improving Wait Events ===<br />
<br />
Bertnard- Add more details to wait events, for example when buffer content could have relfilenode and other information included. Won't be the same details for each wait event and so we have different data we want to add and the number of different details. Buffer content we might have 3 additional details, for a checkpoint we might have 2 extra items. Store this in session dynamically and then be able to return data from pg_stat_activity or otherwise. Issue with consistency. Currently we have wait event and wait event type with int32 and that is always consistent but if additional information is included then not sure about how to keep it consistent.<br />
<br />
Andres- Issue with overheard too. Wait events added because they're cheap but adding this other info adds a lot of additional overhead in certain code paths.<br />
<br />
Bertnard- Yes, have to consider that.<br />
<br />
Andres- Still have to store all the source data with each different wait event. Not sure how to do that without making it much more expensive.<br />
<br />
Bertnard- Have to see how to measure it, maybe able to make it lossy to address that cost.<br />
<br />
Peter E- How would you expose it beyond just pg_stat_activity. The more detail you add such as how extensions may want to include means you have to consider how to display it. How are people supposed to use it?<br />
<br />
Andres- Depends on the details. On content lock on a btree page is very different from contention on content lock for heap page.<br />
<br />
Alvaro- Is waitevent the best way to store this information. Maybe could write to ring buffer and could from application side read that and build a history of what's been going on instead of having to poll that information.<br />
<br />
Peter E- Could still be the wait event API and just store it in a different place<br />
<br />
Andres- We use wait events in critical sections where you can't allocate things and can't do anything serious because heavy locks are being held. Making wait events much more expensive isn't going to be acceptable.<br />
<br />
Peter E- Is consistency really required in all these cases, maybe we don't need to have it be completely consistent? Maybe just write 4 int32 fields without locking around them all at once and maybe it's fine to do that independently.<br />
<br />
Andres- Have to be careful to not make it vastly more expensive. When you read you need to know if what you read is actually valid or not. You can't read it without knowing if it's actually reasonable or not.<br />
<br />
Bertnard- During 10s you have a bunch of different wait events if some aren't valid maybe is ok but you need to know that it's valid.<br />
<br />
Peter E- Would be really frustrating if you get the wrong data and take action based on incorrect data.<br />
<br />
Bertnard- Is it work it to spend time on this?<br />
<br />
Peter E- Could do some simple tests by making value 8 bytes (maybe larger) and putting a spinlock around it and see how expensive it is.<br />
<br />
Andres- 8 bytes probably fine<br />
<br />
Stephen- 8 bytes not enough though to track this<br />
<br />
Andres- 8 bytes atomic on nearly all platforms these days, isn't on like armv7 but probably not a big deal there<br />
<br />
Peter E- Is 8 bytes enough?<br />
<br />
Bertnard- Depends on the wait event<br />
<br />
Peter E- Maybe say "here are the things thinking about adding, this this and this" and if it fits in 8 bytes then maybe ok but if it doesn't then may need another idea.<br />
<br />
Andres- Suspect overhead is going to be too high and will need a completely different mechanism because collecting all that data for all wait events and most of the time it's not going to be needed and is just expensive.<br />
<br />
Stephen- Maybe pull together other information at the same time when polling rather than putting it all in the wait event<br />
<br />
Andres- yeah, maybe store buffer ID then good chance you'll be able to figure out what it is without having to store everything in to the wait event<br />
<br />
Bertnard- Sticking to 8-byte only might be ok<br />
<br />
Andres- store the buffer ID and then get the rest from shared buffers and doesn't introduce a lot of overhead by default. Some of this is maybe solved by dtrace instead possibly.<br />
<br />
Bertnard- Most of the time you have to guess when you have a waitevent but you don't know what is happening. Would like to know if it's always the same relation and see what's going on in an aggregate. If database is waiting on something but you don't know what it's waiting on then that's not as helpful.<br />
<br />
Andres- Maybe infer from other information and not try to have everything answered by data provided through wait event<br />
<br />
Alvaro- Would be good to see what the system is doing in more granular way but wait event isn't the best way to get at that and maybe there should be another way that's a completely different approach which could be turned on/off for a specific operation that doesn't cause too much overhead. idk if things like a branch testing a flag will be too expensive of a problem. Storage of the performance data storage is going to have to be something completely separate from wait event. idea of using a ring buffer to store that data instead.<br />
<br />
Andres- In that case you have to be even more careful of storing the data because the cache line where that ring buffer data is stored and you constantly are writing then it's a significant amount of system memory being used.<br />
<br />
Peter E- Probes need to be put at a different level<br />
<br />
Andres- If you want the granularity where wait events because that's why wait events are there.<br />
<br />
Alvaro- Maybe where dtrace points are<br />
<br />
Mark- Could perhaps clear things out every so often<br />
<br />
Andres- Data-dependent branches added to this to collect numbers the overhead is going to be way higher. Ring buffer idea, would have to be very small ring buffer to avoid too much overhead and have to poll very very often and that all ends up with a lot of overhead.<br />
<br />
Mark- Don't have a specific design but if you overwrite regularly a particular place<br />
<br />
Andres- but then you have a memory barrier and you get a stall if you don't have that data in L1. As soon as you do any reads it gets much more expensive and you need to do reads in the data collection path.<br />
<br />
=== Extensions & Stats ===<br />
<br />
Bertnard- Folks are working on this and want to make sure the idea is generally supported. Idea is to allow extensions to add stats into the system.<br />
<br />
Andres- Add infra to add stats at runtime. pg_stat_statements has its own storage but if we added the last bit of extensibility to the shared memory stats system then maybe wouldn't be needed.<br />
<br />
Bertnard- If you want to reset stats then maybe have it in a different file..<br />
<br />
Andres- Why?<br />
<br />
Peter E- Storage happens just at shutdown<br />
<br />
Andres- When you store it on disk need to keep track of what extension added the stats. With different files maybe you have an easier time detecting which file goes with which extensions stats.<br />
<br />
Peter E- Same issue as always, extensions have to register themselves somehow<br />
<br />
Andres- Maybe just extension name would be fine, just write to disk on shutdown, maybe a bit more space but probably not an issue really. One thing I'd like to change pg_statistic would be to make it crash safe because on crash we run into problems where vacuum doesn't do anything initially because the stats were lost. Maybe store with redo LSN on checkpoint the stats at that point in time and might be slightly dated but would otherwise be correct.<br />
<br />
Heikki- Is there a case where having old stats is worse than new stats..?<br />
<br />
Matthias- What about truncation or such?<br />
<br />
Andres- That should create a new relfilenode and that should be ok<br />
<br />
Heikki- what if stats say it doesn't need vacuum but changes since last time make it so that it does need to<br />
<br />
Andres- Today that problem already exists, this would make things at least better a bit. Could change most of the stats to include relfilenode and then use that when doing replay maybe and should solve truncate problem too. Not sure if there is semantic issue with that.<br />
<br />
Vik- If autovacuum sees 4 zeros then maybe it should select that table for analyze<br />
<br />
Andres- on stat reset then autovacuum goes crazy and that could cause an issue.<br />
<br />
Vik- Also issue with failover where we don't have stats<br />
<br />
Andres- If we add relfilenode to stats key then that would help with failover too and you could count the number of inserts and updates and such and keep that and that would be better than zero. May also be able to serialize stats into xlog during checkpoint maybe and that works maybe for inserts and updates but not for selects because those are actually different on the replicas vs. the primary.<br />
<br />
Peter E- Maybe the standby only replays the things that it trusts or which it should, but that could be messy.<br />
<br />
Alvaro- What about WAL size increase<br />
<br />
Andres- We used to write out the stats a whole bunch and wasn't an issue really. Have seen cases with really huge stats but was very exceptional case. We could do something like a summary at commit time maybe and might make reconsiliation in memory easier.<br />
<br />
Tomas- Only write out the things that changed since the last time... <br />
<br />
Andres- Could add a change counter or such to the in-memory so that we could know when we need to pass things along<br />
<br />
Heikki- Maybe add columns to pg_class to track<br />
<br />
Andres- Update so frequently that it could be a problem. Have to have some kind of per-database background worker of some kind perhaps.<br />
<br />
Tomas- When we store last vacuumed / last analyzed, maybe store at that moment..<br />
<br />
Andres- but at that point it's probably not useful, wouldn't end up triggering another vacuum because it was just run. Logging to WAL at checkpoint time is easy but if you are doing catalog updates then you have to connect to each database to update those catalogs if it's in pg_class, etc.<br />
<br />
Tomas- If we had columns in pg_class, what use-case would that solve that regular logging of stats wouldn't? If we log in WAL stats, would that give you everything you need. Benefit of pg_class would be that you wouldn't lose stats because they're WAL'd.<br />
<br />
Heikki- You could do it differently<br />
<br />
Tomas- Losing stats is a pretty common issue. Two different approaches to the problem- WAL log stats directly vs. updating pg_class. Seems like storing stats in WAL would be better. Once in a while flush modified stats to WAL.<br />
<br />
Andres- Just changing the key to the relfilenode likely would help but wouldn't deal with insert/abort but could handle that by logging more info during abort. With relfilenode we could track enough to get close enough value.<br />
<br />
Heikki- Talking 3 approaches. 1) never WAL log stats but instead calculate stats based on WAL data seen; issue: stats on primary vs. replica they could drift apart- basically dead reckoning, might get far off<br />
<br />
Tomas- How would this work? pg_stats has a lot of other stuff and so you wouldn't have background writer info or checkpointer<br />
<br />
Andres- Why do you want that from the primary when you're on the replica?<br />
<br />
Tomas- Just spit-balling, maybe there's other types of stats that do make sense<br />
<br />
Heikki- Number of stats that you'd want separate on the replica from the primary like seq scans, index scans, etc. Second proposal, instead of dead reckoning, you dump the whole stats file to the WAL on a regular basis and that could be very large which seems like an issue.<br />
<br />
Andres- The size doesn't seem that bad<br />
<br />
Stephen- Maybe store into new place on replica and pull into place on promotion<br />
<br />
Andres- Requires handling of the stats differently quite a bit possibly<br />
<br />
Heikki- 3) Put stats in pg_class directly, not everything but important things<br />
<br />
Andres- That seems like it would be very hard<br />
<br />
Peter E- Saying we only care about these stats for these specific reasons, but not other stats, which isn't great because people care about the other information. Maybe is ok but maybe not.<br />
<br />
Heikki- With any of these schemes, it seems like we would want to separate these<br />
<br />
Andres- Think we agree that trying to keep some stats after crash would be good<br />
<br />
Peter E- We can't hard-code too much stuff if we want to keep stats system extensible<br />
<br />
Andres- Extending stats comes with a bunch of things to be added but shouldn't be too hard to keep extensible even with these ideas.<br />
<br />
=== Container sets (arrays, row types, etc) ===<br />
<br />
Vik- Range type- We have a couple by default but otherwise you have to create your own range, other types get created each time. How can we have multi-type values without having to create new types to do it. What would it take to get multi-sets?<br />
<br />
Peter E- Create them on the fly<br />
<br />
Heikki- Do the same thing as row types, there's permanent row types and also dynamic row types<br />
<br />
Peter E- Want to create a multi-set field with integer and maybe create that type on the fly.<br />
<br />
Vik- Yes, but just in queries it would be nice to create multi-set without having to create a whole new type<br />
<br />
Andres- We don't necessarily need a different pg_type if we can put some encoded into typenum maybe<br />
<br />
Vik- What about nesting?<br />
<br />
Heikki- If you think of them as records, think it works<br />
<br />
Peter E- arrays of multi-sets?<br />
<br />
Andres- Is nesting necessary?<br />
<br />
Vik- Multi-sets useful, maybe not nesting but maybe, multi-set of arrays<br />
<br />
Andres- If you can get a lot of things without implementing a lot of crazy stuff then maybe it could be done.<br />
<br />
Peter E- Is it really a problem to create types?<br />
<br />
Andres- Could end up bloating pg_type a lot<br />
<br />
Peter E- Where is bloat coming from?<br />
<br />
Andres- row types in pg_class ends up adding up a lot<br />
<br />
Alvaro- Also need to consider pg_depend, pg_shdepend for owner<br />
<br />
Peter E- bloat from pg_type ends up coming from every table having entry, maybe create new base type.. Creating 5 is maybe not that bad since creating 2 already. Maybe we just say we don't support ranges on table row types.<br />
<br />
Heikki- Multi-set of record would make sense<br />
<br />
Vik- Yeah. Main issue is knowing about these things on the fly and not necessarily having to put something into pg_type<br />
<br />
Andres- Maybe copy approach from records, might not be too hard except for nesting case.<br />
<br />
=== v16 Patch Triage ===<br />
<br />
session variables, LET command -- Tomas- Will be talking to Pavel about this patch. Did a review of it, planning to commit it, biggest question is if it's really a useful feature or not. I think it is. Patch in pretty good shape. Joe- Like the feature but not sure why it has taken so long. Alvaro- Has gone through several rewrites. Jeff- Risk of running afoul of SQL standard? Tomas- Don't think there really is. Heikki- Are there concerns about what happens if it changes in the middle of a query or..? Tomas- Having session variables that's accessible instead of GUC. It's not transactional. Vik- Why not just use a table? Heikki- Seems like a temp table with only one row? Stephen- Issues with temp tables being constantly created/dropped can't use on standby, etc. Peter E- May look into the standard and see. Tomas- Maybe not good to get into details on the patch right now. Heikki- Looking at patch now.<br />
<br />
Remove self join on a unique column -- Tomas- patch seems correct but is hard to convince myself that people actually write joins like this. Stephen- Because of ORMs. Tomas- Doesn't add much overhead.<br />
<br />
Avoid hiding shared filesets in pg_ls_tmpdir (pg_ls_* functions for showing metadata ...) -- Alvaro- Need to do something here but not sure if this is the thing to do. Andres- doesn't show directories but parallel operation have directories and this wasn't updated and so semantics are not entirely clear.<br />
<br />
Make message at end-of-recovery less scary -- Andres- Idea of patch is quite useful, needs a good bit of polish based on last review. Not sure if that's changed more recently. Vik- Not just wording? Andres- No, 300-line patch and some of that is tests but is more than just wording. Currently we hide errors for example in some places and you get a useless message at the end and to fix that there are structural changes needed. Heikki- seems pretty narrow, if WAL recovery ends due to invalid length but it could end for a variety of reasons depending on if WAL recycled or not. Andres- On primary shouldn't get that and almost always zero out the page. On the standby we should but we don't zero out the pages and that is causing bugs and we should start doing that. Wrote a patch for that but some details are really hard to get right there.<br />
<br />
More scalable multixacts buffers and locking -- Andres- Not sure if there is agreement that this is a good idea because people want to move SLRUs into shared buffers and then this idea wouldn't make sense. Matthias- When is that going to happen? Is a bandaide but could help. Andres- But is a bandaid that could cause really weird performance impacts. Needs a lot of work to figure out the access patterns and such. If was just a config without massive downsides then it would be ok but it isn't that.<br />
<br />
pg_dump - read data for some options from external file -- Peter E- Don't personally like it but if someone wants to commit it then it should be fine. Stephen- Dislike having a whole new file format but whatever.<br />
<br />
CREATE INDEX CONCURRENTLY on partitioned table -- Matthias- Just like normal CONCURRENTLY but on a partitioned table. Heikki- Great feature if we can have it. Are there concerns? Andres- Not sure how the code can be correct, but maybe missing something. Opens a memory context and then calls existing concurrent code and expects snapshots to work across that but that can't really work so don't see how it could be correct... <br />
<br />
Function to log backtrace of postgres processes -- Peter E- Not sure if that's useful? Andres- Wished for this many times. Disagreements on list with this currently. Peter E- Maybe patch tries to do too much? Heikki- Every background worker has to be modified. Peter E- Probably isn't great that it requires that and maybe that's part of the issue. Andres- Does that to make it safe to use in signal handlers.. but it can't do it safely.. Whole reason it does it as shared preload library but that's not guaranteed because of how ELF works. Heikki- Any way to do it safely? Peter E- If you want to call it from a signal handler because you're stuck somewhere.. Andres- Does it really need to be called from a signal handler? Andres- If we use latch wait in more places and use that approach instead of trying to do it from signal handler then it may work. Heikki- Tom commented that surely this is unsafe to do from a signal handler. Stephen- Seems like general feeling is that this should be RWF as needing to be redone to not be trying to do this in a signal handler.<br />
<br />
pg_stat_statements and "IN" conditions -- Tomas- About normalization of the strings, variable number of values in the IN list instead of generating each entry it would normalize into smaller number. Feature seems useful where big IN list completely swamps the system. Andres- Adds a GUC? Seems unnecessary. Tomas- Can imagine cases where different numbers generate different plans, can understand why a GUC. In that case we are not differentiating between different types of queries. Peter E- The code looks very straight-forward here. Tomas- Anyone think we shouldn't have the feature or maybe we don't need to even have the GUC? Vik- Feature seems useful and we should just always enable it. Peter E- Discussion of query jumbling or if we need a switch and this might be something where we may want to have control over. Tomas- We should make the same decision between this patch and query jumbling. If it's hidden behind a GUC or internal function that says jumble one way or another.. Peter E- May be a good release to try putting this into when we're breaking things already and see what happens, if you break it, break it big. Maybe we should just do it. Andres- Anyone know why this adds a new field to struct location len for merge? Tomas- wants to track the original location to the unjumbled. Stephen- Seems like folks are generally in favor of this, maybe even without having a GUC.<br />
<br />
Fix pg_rewind race condition just after promotion -- Heikki- Completely forgot about this and am looking back through it. Just haven't gotten around to actually committing. Heikki will commit (haha, but probably).<br />
<br />
Faster pglz compression -- Tomas- Looks ready, plan to commit it. Difficult to understand but a good improvement. Heikki- Not sure about why to bother but don't see a downside. Tomas- People still do use pglz a lot, so.<br />
<br />
Parallel Hash Full Join -- Alvaro- Munro says planning to get this in shortly ... in November. Heikki- We want it. Seems to include bug fixes that should be committed?<br />
<br />
On client login event trigger -- Heikki- What have the problems been with it? Andres- If you screw it up you can never log in again which was one of the issues. At some point was work on a GUC to disable to allow you to get in.. Not sure if added but without that means no way to log into the system. Alvaro- Very wanted feature. Heikki- What do people want to do with this? Matthias- Possibly useful to set variables on log in or to log into a table that a user logged in. Peter E- Maybe wait until after event trigger disable GUC so that can bypass this if there is a bug or issue with it.<br />
<br />
Consider parallel for LATERAL subqueries having LIMIT/OFFSET -- Tomas- I may be able to take a look but difficult to make reasoning about if it's correct or not, would be good to get Tom's input, but will take a look. Alvaro- Tom said he didn't know how it could be safe. Tomas- I'll read it and maybe learn something and try to figure it out and see if it could be done.<br />
<br />
pg_stat_statements: Track statement entry timestamp -- Andres- A lot of complexity. Tomas- The idea of tracking when entry added makes sense because if you have two entries for two tables and one has very large numbers and other has very low numbers, does it mean if one is more active? Might just be because of which one is newer and not which is more active really. Makes sense. But then adds a lot of complexity by adding in a lot of ways to reset things. Concerned about some of the changes. Andres- A lot of overhead been added lately and not sure if it's good to add more. Tomas- To do reasonable analysis you need to keep the deltas anyway and so not sure that this is really helpful. Peter E- If you have a data set where you care about tracking then likely you'll have entries for years and therefore isn't really that useful. Matthias- Even latest isn't that hard to derive by checking deltas across time. Tomas- Only issue with keeping regular snapshot is that it doesn't work for min/max latency for the query because once you get a spike you'll never see the new min/max in the following period but even so not sure that it makes sense to keep entry timestamp.<br />
<br />
psql - refactor echo code -- Peter E- Added myself to review it and will do so.<br />
<br />
pg_stats and range statistics -- Tomas- Did review of this. What it does is that we don't currently track range statistics and only problem with that is how we read and print the histogram and if there is a way to do that in pure SQL or if we need special functions for it. I will continue working on it and reviewing it and hopefully will make progress.<br />
<br />
pgbench: using prepared BEGIN statement in a pipeline could cause an error -- Alvaro- problem is that we prepare the whole thing, but maybe we didn't want it to change how we are measuring latency and a different method was proposed but the author hasn't changed it accordingly. Alvaro will comment that it wasn't updated to new approach.<br />
<br />
Add system view tracking shared buffer actions -- Andres planning to commit it, issue with tablespace tests but should be able to resolve in next few days.<br />
<br />
Using each rel as both outer and inner for anti-joins -- Tomas- Will make us consider more planning options. Currently only consider one way and this could allow other ways to be considered. Andres- Turns a lot of nested loop antijoins into hash antijoins which seems good. Tomas- Seems pretty reasonable..<br />
<br />
Dynamic result sets from procedures -- Peter E- Patch held up for a long time to get the display of multiple result sets due to psql needing it. Working on adding more capabilities and tests to check the extended protocol, found some issues and that's in progress for being fixed. Not sure if this patch will land any time soon but needs more tests and is a useful feature. Funtionality is part of the standard. Heikki- Changes the protocol? Peter E- Kind of, protocol kind of just works today but maybe need to be more explicit to make sure that everything works. Have a patch to make it work with JDBC that's pretty small.<br />
<br />
Add foreign-server health checks infrastructure -- <br />
<br />
Parallelize correlated subqueries that execute within each worker -- Tomas- On list comments that it's unsafe but the discussion was side-tracked about discussion about how parameters passed to parallel workers. Not sure ... Not just about parallel subqueries or parallelism in general but also about how parameters are passed in general. Not sure what the conclusion is. Andres- Not close to being committable due to commented out warnings and seems to be WIP.<br />
<br />
postgres_fdw: commit remote (sub)transactions in parallel during pre-commit -- Andres- looks partially committed? Heikki- Not sure why this needs to be configurable? Andres- Seems to maybe have a lot of duplicated cases that shouldn't be needed between commit/abort?<br />
<br />
Update relfrozenxmin when truncating temp tables -- Andres- Every version seems to get more complicated ... <br />
<br />
functions to compute size of schemas/AMs (and maybe \dn++ and \dA++) -- Matthias- Would like more verbose options into backslash commands. Peter E- Not sure why want this ++. Maybe have + for more details but don't want to compute size every time. Stephen- Maybe have cache or stats for size of things to make them less expensive to query. Andres- Lot of work to actually keep correct answer for size in shared memory. Andres- Don't really see point and maybe just reject it.<br />
<br />
disallow HEAP_XMAX_COMMITTED and HEAP_XMAX_IS_LOCKED_ONLY -- Andres- just explicitly forbids a combination of bits that shouldn't be allowed. Mark- Mainly to pick up on corruption but not sure that it's actually not allowed to happen and pg_upgrade makes things very difficult because couldn't be 100% sure that this is an error. Seems probably right but not 100% sure. Andres- What does this actually get us though? Would it really catch corruption? Mark- Unless there is a way to prove that this really won't happen then can't commit it. Heikki- Same as having asserts to check things. Tomas- In some other cases have realized that there was corruption due to invalid bits being set and so this could be useful. Don't know how long it has been broken though. Peter E- Maybe add this to amcheck but not add an assertion as that's only in development anyway but won't help with corruption detection. Mark- idea is to add assertion to the code that matches what amcheck checks so if you decide to use such a bit pattern then would check and make sure that it gets realized that both need to be changed. Mark- Not willing to try and guarantee that this can't happen. Heikki- Maybe put it into amcheck and use that to see if it does happen in the field. Tomas- It might scare people though for no reason if it turns out to not be an issue and people who hit it might not report it. Heikki- another thing is that it seems to possibly report problem on pg_upgrade'd clusters which were valid and therefore this shouldn't go in because of that. Maybe doesn't kill the whole patch but maybe does.<br />
<br />
In-place persistence change of a relation (fast ALTER TABLE ... SET LOGGED with wal_level=minimal) -- Peter E- Seems to add a lot of code but seems not really worth it. Andres- Should have removed minimal WAL long ago. Tomas- Lots of bugs there and people don't seem interested in fixing them..? Andres- Some of them fixed but those fixes sometimes added other bugs. Tomas- Maybe make minimal WAL level improvements conditional on other things. Andres- Don't see real use-case for wal level minimal. Tomas- Wouldn't use it for important data ... Peter E- Even if we don't like wal level minimal, this is a legit point that we could optimize this, but the code is large and adds things to check what we changed, etc. Tomas- For patch author it makes sense because it can be helpful. Heikki- Patch also just changes how relation rewrite is done to just use FPIs instead of a bunch of heap inserts and that could be better. Maybe get rid of wal level minimal stuff but keep the other changes. Andres- Not sure if this is really safe to do this way though like in rollback. Tomas- Should be at least split into two patches if it actually works, a patch for the non-wal-level-minimal part and then a patch for the wal-level-minimal optimization.<br />
<br />
Speed up releasing of locks -- Matthias- Good idea. Andres- Needs a bit more work and possible small slowdowns. Removing a lot of weird code. Doable for 16 if time is put into it.<br />
<br />
Add log messages when replication slots become active and inactive -- Tomas- seems like a simple patch if we want them, which seems reasonable we can have it. Doable for 16 if we want them.<br />
<br />
Daitch-Mokotoff soundex -- Tomas- Seems like a simple patch and will take a look and probably will commit it.<br />
<br />
reduce impact of lengthy startup and checkpoint tasks -- Andres- Have serious doubts about it making things better for xid wraparound and other things. Good idea in theory but need much more pared down set of things as said on thread. Pretty large change and probably not for 16 unless a committer picks it up and spends a lot of time on it.<br />
<br />
Add Amcheck option for checking unique constraints in btree indexes -- Mark- Responded on a couple of things, author submitted new patches, waiting for Peter G to see if he wants it. Probably doable if Peter G has time to review it.<br />
<br />
pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory -- Probably can go in as a bugfix?<br />
<br />
Error "initial slot snapshot too large" in create replication slot -- Andres- still couldn't figure out how to do much better than the current state. Not sure if anything new has happened.<br />
<br />
AcquireExecutorLocks() and run-time pruning -- Tomas- Amit is working on it and getting feedback from Tom and so seems to be in progress.<br />
<br />
64-bit SLRU page numbers (independent part of 64-bit XIDs) -- Heikki- seems like a good idea but not sure about implementation. Peter E- Not filled with confidence about it. Heikki- Is this independently useful? Matthias- Good to have in before 64bit xid because it reduces the patch size. Andres- could be useful with a different AM. Matthias- Also for the whole SLRUs and so for MultiXact it might help those too. Peter E- Asked why this is helpful, may have been changed? Matthias- Preparation for 64bit xids. Peter E- Question on whole patchset seems like things get added and then reverted in the patch series and is a bit confusing. Heikki- Looking at patch, it doesn't change more things..? There's some complicated logic in dealing with wraparound and switching to 64bit numbers should help with that but this patch doesn't seem to take advantage of that. Andres- would have to make pg_upgrade quite a bit more complicated to make it work. Heikki- There is a pg_upgrade part of the patch. Andres- not likely to make it into 16.<br />
<br />
Pluggable toaster -- Andres- Don't see it going anyway and idea of content aware toasting is very complicated and patch adds a whole bunch of infra. Vik- Like the idea but is very complicated. Heikki- like the idea of making the toaster better. Matthias- For certain data types, specialized compression would be really good. Tomas- Seems like this isn't the right place to be putting this infra. Andres- want to compress json to get rid of keys, want to do it for everything not just toasted data and seems like isn't the right place to do this. Tomas- Seems like the wrong level. Want dictionary and use that for the data type and then compress and then it can be toasted like usual. Matthias- Not really a good way to make this available. Andres- This doesn't really get you much farther. Heikki- Seems actually more reasonable than thought. Two types of toasting, the compression and slicing data into tuples and putting in toast table. Matthias- This does both and tries to work with the data type to make the output more performant to access. json tuple deconstructed into multiple tuples following the structure. There have been some really compelling performance improvements using this. Heikki- Maybe be able to split this by the two different pieces. Very unlikely for 16 due to lack of consensus.<br />
<br />
Add pg_stat_session -- Peter E- Seems reasonable to make it into 16 as long as agreement about usefulness. Needs someone to look at it. Maybe move some things from pg_stat_activity to here?<br />
<br />
Allow parallel plan for referential integrity checks -- Mark- Robert marked it as unsafe because he wasn't sure if it was safe. Author doesn't seem to have time. Needs someone to pick it up or it should be closed or punted to 17.<br />
<br />
warn if GUC set to an invalid shared library -- Seems to need some cleanup? Hopefully someone can look at it, not a lot of code and could probably make it if worked on.<br />
<br />
add guc: hugepages_active -- Seems reasonable.<br />
<br />
Time-delayed logical replication subscriber -- Peter E- seems to be getting worked on, could be done in time.<br />
<br />
Add non-blocking version of PQcancel -- Heikki- Seems like a good idea in priciple. Peter E- being worked on and plausible for 16.<br />
<br />
Add LZ4 compression in pg_dump -- Tomas- seems almost ready and have been reviewing it, probably good enough, likely for 16.<br />
<br />
Move SLRU data into the regular buffer pool -- Andres- Probably not for 16 at this point. Heikki- Concern about performance. Matthias- Performance seems ok. Heikki- probably not going to make 16 just because it's quite large. Andres- Deletes more code than it adds at least.<br />
<br />
doc: PQexecParams binary handling example for REAL data type -- Peter E- being worked on, should be fine.<br />
<br />
Support logical replication of DDL commands -- Not likely to make it to 16 as it's quite large.<br />
<br />
Skip replicating the tables specified in except table option -- Alvaro- seems like it needs some work, not sure if it'll be ok for 16.<br />
<br />
Data is copied twice when specifying both child and parent table in publication -- Sounds like a bug?<br />
<br />
Perform streaming logical transactions by background workers -- Partially committed?<br />
<br />
Fix dsa_free() to re-bin segment -- bug fix?<br />
<br />
pg_rewind: warn when checkpoint hasn't happened after promotion -- Heikki- Looking, not a large patch, seems sane are probably could make it.<br />
<br />
generate_series in selected timezone, date_add in selected timezone -- no opinions<br />
<br />
New hooks in the connection path -- Bertrand will update to remove hook which seems contentious and hopefully the rest is ok to go in.<br />
<br />
Check consistency of GUC defaults between .sample.conf and pg_settings.boot_val -- Andres- Good idea but was a competing patch, not sure which way will go.<br />
<br />
nbtree performance improvements through specialization on key shape -- Matthias- Needs some cleanup. Andres- Seems like too large a patch to make it in. Matt- Ask Peter G to review it? Matthias- Not sure how to make it much better than how it is.<br />
<br />
Add sortsupport for range types and btree_gist -- Jeff- I can probably take a look and see. Not sure what state it's in.<br />
<br />
Reducing planning time when tables have many partitions -- Alvaro- Rowley has been working on it.<br />
<br />
CI and test improvements -- <br />
<br />
Transparent column encryption -- Peter E- feels like it's complete.. Want to try and get it in and make it acceptable <br />
<br />
Switching XLog source from archive to streaming when primary available -- Andres- pretty reasonable patch, haven't looked at details but having a config option for this seems reasonable and could probably go in for 16.<br />
<br />
An attempt to avoid locally-committed-but-not-replicated-to-standby-transactions in synchronous replication -- Andres- Not sure why this needs to be solved..? Tomas- Seems backwards from what the streaming sync replication does? We commit locally and then wait and so there shouldn't be more than one waiting. Andres- Busy loop which doesn't seem good? Not sure about this one.<br />
<br />
Minimal logical decoding on standbys -- Bertrand- A lot of activity with feedback from Robert and Andres. Andres- Good chance that at least some of it could make it into 16.<br />
<br />
Compression dictionaries for JSONB -- Alvaro- Related to toasting patch? Heikki- Why just do this for jsonb? Matthias- Specifically implemented for jsonb but should make it possible for others too? Don't think it will make 16 because don't have bandwidth and not a lot of others interested. Tomas- Think it actually does the infra. Main problem I had with the patch is I tried to measure the benefit to show improvement and had trouble seeing consistent improvements. Not sure if that was my problem but we need to decide if we want to do this or pluggable toaster or what. Andres- Uses typmod seems like a no-go for this? Tomas- data type specific / column type specific compression, we need context to identify the dictionary, patch is using typmod for that which doesn't seem good. Heikki- seems like would belong better in the toaster. Alvaro- maybe have a half-hour discussion with the devs around these things. Andres- Seems to require the dictionary be specified which doesn't seem good. Tomas- Just initial implementation, in future would be a process to handle doing that. Not likely for 16 just because these questions need to be figured out and discussed more. These are ok in POC but not going to be good enough to go in yet. Andres- Maybe dictionary go into pg_attribute or other context. Does not seem likely for 16.<br />
<br />
ALTER TABLE SET ACCESS METHOD on partitioned tables -- Seems small enough and useful enough that could make it for 16.<br />
<br />
Add SPLIT PARTITION/MERGE PARTITIONS commands -- Alvaro- Definitely want this but not sure we are going to be able to make it for 16.<br />
<br />
Fix assertion failure with barriers in parallel hash join -- Bug fix?<br />
<br />
Support load balancing in libpq -- Andres- Not a very large patch. Tomas- Reasonable and may be able to make it in for 16.<br />
<br />
Add JIT deform_counter -- <br />
<br />
Amcheck verification of GiST and GIN -- <br />
<br />
Use fadvise in wal replay -- Andres- reject it. Tomas- Whole assumption is readahead is disabled, but if readahead is enabled then this is always worse. Nothing to solve here really.<br />
<br />
Let libpq reject unexpected authentication requests -- Andres- doesn't address issue with peer, at least. Solve some problems maybe. Need to be clear in the documentation what it is actually doing. Could possibly make 16.<br />
<br />
Support % wildcard in extension upgrade scripts -- Andres- Think this was pretty much rejected?<br />
<br />
Fix recovery conflict SIGUSR1 handling -- bug fix<br />
<br />
pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum -- bug fix<br />
<br />
Add 64-bit XIDs into PostgreSQL 16 -- Not gonna make it for 16.<br />
<br />
Eliminating SPI from RI triggers -- Alvaro- Seems not likely to happen due to people being too busy with other things. Tomas- Was updated though? Maybe.<br />
<br />
Add initdb option to initialize cluster with non-standard xid/mxid/mxoff. -- For testing 64bit patch but could be useful for other things. Mainly for testing.<br />
<br />
Testing autovacuum wraparound -- Andres- Not planning on working on it really because we lack infra to do it without problems.<br />
<br />
Improve dead tuple storage for lazy vacuum -- Andres- Making progress, not sure it'll be ready.<br />
<br />
USAGE privilege on PUBLICATION --<br />
<br />
explain analyze rows=%.0f --<br />
<br />
Fix alter subscription concurrency errors --<br />
<br />
ALTER TABLE and CLUSTER fail to use a BulkInsertState for toast tables --<br />
<br />
Cygwin cleanup --<br />
<br />
logical decoding and replication of sequences, take 2 --<br />
<br />
doc: mention CREATE+ATTACH PARTITION as an alternative to CREATE..PARTITION OF --<br />
<br />
Add index scan progress to pg_stat_progress_vacuum --</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=Todo&diff=37432Todo2023-01-04T04:52:36Z<p>Davidrowley: /* Optimizer / Executor */ Adjust OPTIMIZER_DEBUG item to try to reduce the chances of someone thinking we just want to enable that output by setting a GUC</p>
<hr />
<div><div style="margin: 1ex 1em; float: right;"><br />
__TOC__<br />
</div><br />
<br />
This list contains some known PostgreSQL bugs, some feature requests, and some things we are not even sure we want. Many of these items are hard, and some are perhaps impossible. If you would like to work on an item, please read the [[Developer FAQ]] first. There is also a [[Development_information|development information page]].<br />
<br />
* {{TodoPending}} - marks ordinary, incomplete items<br />
* {{TodoEasy}} - marks items that are easier to implement<br />
* {{TodoDone}} - marks changes that are done, and will appear in the PostgreSQL 15 release.<br />
<br />
Over time, it may become clear that a TODO item has become outdated or otherwise determined to be either too controversial or not worth the development effort. Such items should be retired to the [[Not Worth Doing]] page.<br />
<br />
For help on editing this list, please see [[Talk:Todo]]. <b>Please do not add or remove items here without discussion on the [[Mailing_Lists|mailing list]].</b><br />
<br />
== Development Process ==<br />
<br />
<b>WARNING for Developers:</b> Unfortunately this list does not contain all the information necessary for someone to start coding a feature. Some of these items might have become unnecessary since they were added --- others might be desirable but the implementation might be unclear. When selecting items listed below, be prepared to first discuss the value of the feature. '''Do not assume that you can select one, code it and then expect it to be committed.''' Always discuss design on Hackers list before starting to code. The flow should be:<br />
<br />
Desirability -> Design -> Implement -> Test -> Review -> Commit<br />
<br />
== Administration ==<br />
<br />
{{TodoItem<br />
|Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptly<br />
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php <nowiki>Removing unreferenced files</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow log_min_messages to be specified on a per-module basis<br />
|This would allow administrators to see more detailed information from specific sections of the backend, e.g. checkpoints, autovacuum, etc. Another idea is to allow separate configuration files for each module, or allow arbitrary SET commands to be passed to them. See also [[Logging Brainstorm]].}}<br />
<br />
{{TodoItem<br />
|Prevent query cancel packets from being replayed by an attacker, especially when using SSL<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php <nowiki>Replay attack of query cancel</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider supporting incremental base backups<br />
* http://www.postgresql.org/message-id/543D5AA7.9@2ndquadrant.it<br />
}}<br />
<br />
=== Configuration files ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItemDone<br />
|Allow pg_hba.conf to process include files<br />
* [http://www.postgresql.org/message-id/86fvnm5t44.fsf@jerry.enova.com HBA files w/include support]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block<br />
* Currently it displays zero.<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Tablespaces ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow a database in tablespace t1 with tables created in tablespace t2 to be used as a template for a new database created with default tablespace t2<br />
|Currently all objects in the default database tablespace must have default tablespace specifications. This is because new databases are created by copying directories. If you mix default tablespace tables and tablespace-specified tables in the same directory, creating a new database from such a mixed directory would create a new database with tables that had incorrect explicit tablespaces. To fix this would require modifying pg_class in the newly copied database, which we don't currently do.}}<br />
<br />
{{TodoItem<br />
|Allow reporting of which objects are in which tablespaces<br />
|This item is difficult because a tablespace can contain objects from multiple databases. There is a server-side function that returns the databases which use a specific tablespace, so this requires a tool that will call that function and connect to each database to find the objects in each database for that tablespace.}}<br />
<br />
{{TodoItem<br />
|Allow WAL replay of CREATE TABLESPACE to work when the directory structure on the recovery computer is different from the original<br />
* [https://www.postgresql.org/message-id/flat/CALfoeisEF92F5nJ-aAcuWTvF_Aogxq_1bHLem_kVfM_tHc2mfg%40mail.gmail.com Some possible approaches]<br />
* [https://www.postgresql.org/message-id/20180214042443.GB1993%40paquier.xyz Remarks about the difficulty of the item]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow tablespaces on RAM-based partitions for unlogged tables<br />
* http://archives.postgresql.org/pgsql-advocacy/2011-05/msg00033.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow toast tables to be moved to a different tablespace<br />
* [http://archives.postgresql.org/pgsql-hackers/2011-05/msg00980.php moving toast table to its own tablespace]<br />
* {{messageLink|CAFEQCbH756DyyAPQ1ykh3+b+kE1-EhWRww1WO_x5v38C-uLnUg@mail.gmail.com|patch : Allow toast tables to be moved to a different tablespace}}<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Statistics Collector ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Testing pgstat via pg_regress is tricky and inefficient. Consider making a dedicated pgstat test-suite.<br />
* [http://www.postgresql.org/message-id/20141216142937.GX1768@alvh.no-ip.org <nowiki>Re: REVIEW: Track TRUNCATE via pgstat</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Teach stats collector to differentiate between internal and leaf index pages<br />
* [https://www.postgresql.org/message-id/flat/CAH2-WzmdZqxCS1widYzjDAM%2BZ-Jz%3DejJoaWXDVw9Qy1UsK0tLA%40mail.gmail.com <nowiki>Stats collector's idx_blks_hit value is highly misleading in practice</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== SSL ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
| Allow automatic selection of SSL client certificates from a certificate store<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg00406.php <nowiki>Allow multiple certificates or keys in the postgresql.crt/.key files</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Standby server mode ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
| Prevent variables inherited from the server environment from being used for making streaming replication connections<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg01011.php <nowiki>Re: Parameter name standby_mode</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Data Types ==<br />
<br />
{{TodoItem<br />
|Add support for public SYNONYMs<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php <nowiki>Proposal for SYNONYMS</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php<br />
* http://archives.postgresql.org/pgsql-general/2010-12/msg00139.php<br />
}}<br />
<br />
{{TodoItem<br />
|Consider a special data type for regular expressions<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php <nowiki>Why is there a tsquery data type?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow deleting enumerated values from an existing enumerated data type<br />
* [http://www.postgresql.org/message-id/CAO%3D2mx6uvgPaPDf-rHqG8%3D1MZnGyVDMQeh8zS4euRyyg4D35OQ@mail.gmail.com Alter or rename enum value]<br />
}}<br />
<br />
{{TodoItem<br />
|Add overlaps geometric operators that ignore point overlaps<br />
* http://archives.postgresql.org/pgsql-hackers/2010-03/msg00861.php<br />
}}<br />
<br />
=== Dates and Times ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow infinite intervals just like infinite timestamps<br />
* https://www.postgresql.org/message-id/4EB095C8.1050703@agliodbs.com<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Arrays ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow single-byte header storage for array elements}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Text Search ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Consider changing error to warning for strings larger than one megabyte<br />
* [http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php <nowiki>BUG #3975: tsearch2 index should not bomb out of 1Mb limit</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve default parser, to more easily allow adding new tokens<br />
* http://archives.postgresql.org/message-id/23485.1297727826@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
|Add additional support functions<br />
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg00319.php<br />
}}<br />
<br />
=== XML ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add XML Schema validation and xmlvalidate functions (SQL:2008)}}<br />
<br />
{{TodoItem<br />
|Add xmlvalidatedtd variant to support validating against a DTD?}}<br />
<br />
{{TodoItem<br />
|Relax-NG validation; libxml2 supports this already}}<br />
<br />
{{TodoItem<br />
|Add functions from SQL:2006: XMLDOCUMENT, XMLCAST, XMLTEXT}}<br />
<br />
{{TodoItem<br />
|Add XMLNAMESPACES support in XMLELEMENT and elsewhere}}<br />
<br />
{{TodoItem<br />
|Report errors returned by the XSLT library<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg00562.php<br />
}}<br />
<br />
{{TodoItem<br />
|XML Canonical: Convert XML documents to canonical form to compare them. libxml2 has support for this.}}<br />
<br />
{{TodoItem<br />
|Add pretty-printed XML output option<br />
|Parse a document and serialize it back in some indented form. libxml2 might support this.}}<br />
<br />
{{TodoItem<br />
|Add XMLQUERY (from the SQL/XML standard)}}<br />
<br />
{{TodoItem<br />
|Allow XML shredding<br />
|In some cases shredding could be better option (if there is no need to keep XML docs entirely, e.g. if we have already developed tools that understand only relational data. This would be a separate module that implements annotated schema decomposition technique, similar to DB2 and SQL Server functionality.}}<br />
<br />
{{TodoItem<br />
|XPath: Adding the <x> at the root causes problems [http://archives.postgresql.org/pgsql-bugs/2008-05/msg00184.php] [http://archives.postgresql.org/pgsql-bugs/2008-07/msg00054.php] [http://archives.postgresql.org/pgsql-general/2008-07/msg00613.php]}}<br />
<br />
{{TodoItem<br />
|Verify Xpath escaping behavior<br />
* [http://www.postgresql.org/message-id/E1VOXZv-0008Q9-0Z@wrigleys.postgresql.org Xpath behaviour unintuitive / arguably wrong]<br />
* [http://www.postgresql.org/message-id/CAAY5AM1L83y79rtOZAUJioREO6n4%3DXAFKcGu6qO3hCZE1yJytg@mail.gmail.com xpath missing entity decoding - bug or feature]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Functions ==<br />
<br />
{{TodoItem<br />
|Implement Boyer-Moore searching in LIKE queries<br />
* {{messageLink|27645.1220635769@sss.pgh.pa.us|TODO item: Implement Boyer-Moore searching (First time hacker)}}<br />
* [https://www.postgresql.org/message-id/CALkFZpcbipVJO%3DxVvNQMZ7uLUgHzBn65GdjtBHdeb47QV4XzLw@mail.gmail.com Implement Boyer-Moore searching in LIKE queries]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent malicious functions from being executed with the permissions of unsuspecting users<br />
|Indexed functions are safe, so VACUUM and ANALYZE are safe too. Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable. <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php <nowiki>Some notes about the index-functions security vulnerability</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix /contrib/btree_gist's implementation of inet indexing<br />
* [http://archives.postgresql.org/pgsql-bugs/2010-10/msg00099.php <nowiki>BUG #5705: btree_gist: Index on inet changes query result</nowiki>]<br />
}}<br />
<br />
== Multi-Language Support ==<br />
<br />
{{TodoItem<br />
|Add NCHAR (as distinguished from ordinary varchar)<br />
* [http://www.postgresql.org/message-id/A756FAD7EDC2E24F8CAB7E2F3B5375E918B12BC0@FALEX03.au.fjanz.com UTF8 national character data type support WIP patch and list of open issues.]<br />
}}<br />
<br />
{{TodoItem<br />
|Integrate collations with text search configurations<br />
* [http://archives.postgresql.org/message-id/28887.1303579034@sss.pgh.pa.us <nowiki>Some TODO items for collations</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Integrate collations with to_char() and related functions<br />
* [http://archives.postgresql.org/message-id/28887.1303579034@sss.pgh.pa.us <nowiki>Some TODO items for collations</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Support collation-sensitive equality and hashing functions<br />
* [http://archives.postgresql.org/pgsql-hackers/2011-06/msg00472.php <nowiki> contrib/citext versus collations</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Support multiple simultaneous character sets, per SQL:2008}}<br />
<br />
{{TodoItem<br />
|Improve UTF8 combined character handling?}}<br />
<br />
{{TodoItem<br />
|Fix contrib/fuzzystrmatch to work with multibyte encodings<br />
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00047.php <nowiki> soundex function returns UTF-16 characters</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg00138.php <nowiki> dmetaphone woes</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Change memory allocation for multi-byte functions so memory is allocated inside conversion functions<br />
|Currently we preallocate memory based on worst-case usage.}}<br />
<br />
{{TodoItem<br />
|Add ability to use case-insensitive regular expressions on multi-byte characters<br />
|Currently it works for UTF-8, but not other multi-byte encodings<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg00433.php <nowiki>Regexps vs. locale</nowiki>]<br />
* {{MessageLink|20091201210024.B1393753FB7@cvs.postgresql.org|A partial solution for UTF-8}}<br />
}}<br />
<br />
{{TodoItem<br />
|Improve encoding of connection startup messages sent to the client<br />
|Currently some authentication error messages are sent in the server encoding<br />
* [http://archives.postgresql.org/pgsql-general/2008-12/msg00801.php <nowiki>encoding of PostgreSQL messages</nowiki>]<br />
* [http://www.postgresql.org/message-id/20131220030725.GA1411150@tornado.leadboat.com multibyte messages are displayed incorrectly on the client]<br />
}}<br />
<br />
{{TodoItem<br />
|Windows: Cache MessageEncoding conversion for use outside transactions<br />
* http://www.postgresql.org/message-id/20150812055719.GA1945333@tornado.leadboat.com<br />
}}<br />
<br />
== Views and Rules ==<br />
<br />
{{TodoItem<br />
|Improve ability to modify views via ALTER TABLE<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00691.php <nowiki>Re: idea: storing view source in system catalogs</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg01410.php <nowiki>modifying views</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00300.php <nowiki>Re: patch: Add columns via CREATE OR REPLACE VIEW</nowiki>]<br />
}}<br />
<br />
== SQL Commands ==<br />
<br />
{{TodoItem<br />
|Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT<br />
* [https://www.postgresql.org/message-id/flat/CAJZSWkWN3YwQ01C3%2Bcq0%2BeyZ1DmK%3D69_6vryrsVGMC%3D%2BfWrSZA%40mail.gmail.com/ Adding CORRESPONDING to Set Operations.]<br />
* [http://web.archive.org/web/20161019182747/dissipatedheat.com/2011/11/10/how-not-to-write-a-patch-for-postgresql/ How not to write this patch.]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve type determination of unknown (NULL or quoted literal) result columns for UNION/INTERSECT/EXCEPT<br />
* [http://archives.postgresql.org/message-id/9799.1302719551@sss.pgh.pa.us <nowiki>UNION construct type cast gives poor error message</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow prepared transactions with temporary tables created and dropped in the same transaction, and when an ON COMMIT DELETE ROWS temporary table is accessed<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php <nowiki>Re: &quot;could not open relation 1663/16384/16584: No such file or directory&quot; in a specific combination of transactions with temp tables</nowiki>]<br />
* [http://archives.postgresql.org/message-id/492543D5.9050904@enterprisedb.com A suggestion on how to implement this]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow NOTIFY in rules involving conditionals}}<br />
<br />
{{TodoItem<br />
|Allow LISTEN on patterns<br />
* http://www.postgresql.org/message-id/52693FC5.7070507@gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Simplify dropping roles that have objects in several databases}}<br />
<br />
{{TodoItem<br />
|Add support for WITH RECURSIVE ... CYCLE<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00291.php <nowiki>WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows</nowiki>]}}<br />
<br />
{{TodoItem<br />
|Add DEFAULT .. AS OWNER so permission checks are done as the table owner<br />
|This would be useful for SERIAL nextval() calls and CHECK constraints.}}<br />
<br />
{{TodoItem<br />
|Add comments on system tables/columns using the information in catalogs.sgml<br />
|Ideally the information would be pulled from the SGML file automatically.}}<br />
<br />
{{TodoItem<br />
|Prevent the specification of conflicting transaction read/write options<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-01/msg00684.php <nowiki>Re: SET TRANSACTION and SQL Standard</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow PREPARE of cursors}}<br />
<br />
{{TodoItem<br />
|Have DISCARD PLANS discard plans cached by functions<br />
|DISCARD ALL should do the same.<br />
* http://archives.postgresql.org/pgsql-hackers/2011-01/msg00431.php<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid multiple-evaluation of BETWEEN and IN arguments containing volatile expressions<br />
* http://archives.postgresql.org/message-id/4D95B605.2020709@enterprisedb.com<br />
}}<br />
<br />
=== CREATE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow CREATE TABLE AS to determine column lengths for complex expressions like SELECT col1 || col2}}<br />
<br />
{{TodoItem<br />
|Have WITH CONSTRAINTS also create constraint indexes<br />
* [http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php <nowiki>Re: CREATE TABLE LIKE INCLUDING INDEXES support</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Move NOT NULL constraint information to pg_constraint<br />
|Currently NOT NULL constraints are stored in pg_attribute without any designation of their origins, e.g. primary keys. One manifest problem is that dropping a PRIMARY KEY constraint does not remove the NOT NULL constraint designation. Another issue is that we should probably force NOT NULL to be propagated from parent tables to children, just as CHECK constraints are. (But then does dropping PRIMARY KEY affect children?)<br />
* http://archives.postgresql.org/message-id/19768.1238680878@sss.pgh.pa.us<br />
* http://archives.postgresql.org/message-id/200909181005.n8IA5Ris061239@wwwmaster.postgresql.org<br />
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg01223.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg00358.php<br />
* [https://www.postgresql.org/message-id/CAB7nPqTPXgX9HiyhhtAgpW7jbA1iskMCSoqXPEEB_KYXYy1E1Q@mail.gmail.com Prevent ALTER TABLE DROP NOT NULL on child tables if parent column has it]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent concurrent CREATE TABLE from sometimes returning a cryptic error message<br />
* [http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php <nowiki>BUG #3692: Conflicting create table statements throw unexpected error</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add CREATE SCHEMA ... LIKE that copies a schema}}<br />
<br />
{{TodoItem<br />
|Fix CREATE OR REPLACE FUNCTION to not leave objects depending on the function in inconsistent state<br />
* [http://archives.postgresql.org/pgsql-general/2008-08/msg00985.php indexes on functions and create or replace function]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow temporary tables to exist as empty by default in all sessions<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php <nowiki>what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg01329.php <nowiki>idea: global temp tables</nowiki>]<br />
* [http://archives.postgresql.org//pgsql-hackers/2009-05/msg00016.php <nowiki>Re: idea: global temp tables</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg01098.php <nowiki>global temporary tables</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2012-04/msg01148.php Temporary tables under hot standby]<br />
* [http://www.postgresql.org/message-id/CAFj8pRC2h6qhHsFbcE7b_7SagiS6o%3D5J2UvCwCb05Ka1XFv_Ng@mail.gmail.com Implementation of global temporary tables?]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow the creation of "distinct" types<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01647.php <nowiki>Distinct types</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider analyzing temporary tables when they are first used in a query<br />
|Autovacuum cannot analyze or vacuum temporary tables.<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg00416.php <nowiki>autovacuum and temp tables support</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== UPDATE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Research self-referential UPDATEs that see inconsistent row versions in read-committed mode<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php <nowiki>Concurrently updating an updatable view</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve performance of EvalPlanQual mechanism that rechecks already-updated rows<br />
|This is related to the previous item, which questions whether it even has the right semantics<br />
* [http://archives.postgresql.org/pgsql-bugs/2008-09/msg00045.php <nowiki>BUG #4401: concurrent updates to a table blocks one update indefinitely</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-bugs/2009-07/msg00302.php <nowiki>BUG #4945: Parallel update(s) gone wild</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== ALTER ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Have ALTER TABLE RENAME of a SERIAL column rename the sequence<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php <nowiki>Re: newbie: renaming sequences task</nowiki>]<br />
* [http://archives.postgresql.org/message-id/CADLWmXUV4LbLhMZL8rYMhCy72aZZLB5BSARPQVgoX0BrxA0FFg@mail.gmail.com renaming implicit sequences]<br />
}}<br />
<br />
{{TodoItem<br />
|Add ALTER DOMAIN to modify the underlying data type}}<br />
<br />
{{TodoItem<br />
|Allow ALTER TABLESPACE to move the tablespace to different directories}}<br />
<br />
{{TodoItem<br />
|Allow moving system tables to other tablespaces, where possible<br />
|Currently non-global system tables must be in the default database tablespace. Global system tables can never be moved.}}<br />
<br />
{{TodoItem<br />
|Have ALTER INDEX update the name of a constraint using that index}}<br />
<br />
{{TodoItem<br />
|Allow column display reordering by recording a display, storage, and permanent id for every column?<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php <nowiki>Re: column ordering, was Re: [PATCHES] Enums patch v2</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg01029.php <nowiki>Column reordering in pg_dump</nowiki>]<br />
* http://archives.postgresql.org/message-id/1324412114-sup-9608@alvh.no-ip.org<br />
* [http://www.postgresql.org/message-id/CAApHDvqhnuznxd4xVMFDcGn+nHVYyUtJ-TvbRsOuR%3DPaVbbGqw@mail.gmail.com logical column order and physical column order]<br />
* [http://www.postgresql.org/message-id/20141209174146.GP1768@alvh.no-ip.org logical column ordering]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow deactivating (and reactivating) indexes via ALTER TABLE<br />
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg01191.php<br />
}}<br />
<br />
{{TodoItem<br />
|Add ALTER OPERATOR ... RENAME<br />
|needs to consider effects of changing operator precedence<br />
* [http://archives.postgresql.org/message-id/1322948781.26266.9.camel@vanquo.pezone.net Missing rename support]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== CLUSTER ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Automatically maintain clustering on a table<br />
|This might require some background daemon to maintain clustering during periods of low usage. It might also require tables to be only partially filled for easier reorganization. Another idea would be to create a merged heap/index data file so an index lookup would automatically access the heap data too. A third idea would be to store heap rows in hashed groups, perhaps using a user-supplied hash function.<br />
* [http://archives.postgresql.org/pgsql-performance/2004-08/msg00350.php <nowiki>Equivalent praxis to CLUSTERED INDEX?</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00155.php <nowiki>Re: Grouped Index Tuples</nowiki>]<br />
* http://community.enterprisedb.com/git/<br />
* [http://archives.postgresql.org/pgsql-performance/2009-10/msg00346.php <nowiki>Re: maintain_cluster_order_v5.patch</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
| Allow CLUSTER to be used on partial indexes<br />
* http://www.postgresql.org/message-id/CAMkU%3D1zYwoHHsqJ8wfK3GdG_t_a6t4RK-GFDSKymQ0EGP%3DtypA@mail.gmail.com<br />
}} <br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== COPY ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow COPY to report error lines and continue<br />
|This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure. <br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php <nowiki>Re: VLDB Features</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow COPY to report errors sooner<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php <nowiki>Timely reporting of COPY errors</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow COPY FROM to create index entries in bulk<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php <nowiki>Batch update of indexes on data loading</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve COPY performance<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php <nowiki>Re: 8.3 / 8.2.6 restore comparison</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01882.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow a stalled COPY to exit if the backend is terminated<br />
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00067.php <nowiki>Re: possible bug not in open items</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow COPY "text" format to output a header<br />
* [http://www.postgresql.org/message-id/CACfv+pJ31tesLvncJyP24quo8AE+M0GP6p6MEpwPv6yV8%3DsVHQ@mail.gmail.com Why doesn't COPY support the HEADER options for tab-separated output?]<br />
}}<br />
<br />
{{TodoItem<br />
|Have COPY FREEZE set PD_ALL_VISIBLE<br />
* [http://www.postgresql.org/message-id/CAMkU%3D1w3osJJ2FneELhhNRLxfZitDgp9FPHee08NT2FQFmz_pQ@mail.gmail.com items]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== GRANT/REVOKE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow dropping of a role that has connection rights<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00736.php <nowiki>DROP ROLE dependency tracking ...</nowiki>]<br />
}}<br />
{{TodoEndSubsection}}<br />
<br />
=== DECLARE CURSOR ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Prevent DROP TABLE from dropping a table referenced by its own open cursor?}}<br />
<br />
{{TodoItem<br />
|Provide some guarantees about the behavior of cursors that invoke volatile functions<br />
* [http://archives.postgresql.org/message-id/20997.1244563664@sss.pgh.pa.us Re: Cursor with hold emits the same row more than once across commits in 8.3.7]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== SHOW/SET ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM ANALYZE, and CLUSTER}}<br />
<br />
{{TodoItem<br />
|Rationalize the discrepancy between settings that use values in bytes and SHOW that returns the object count<br />
* [http://archives.postgresql.org/pgsql-docs/2008-07/msg00007.php <nowiki>Re: [ADMIN] shared_buffers and shmmax</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== ANALYZE ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Improve how ANALYZE computes in-doubt tuples<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php <nowiki>VACUUM/ANALYZE counting of in-doubt tuples</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Remove quadratic time in statistics sender when analyzing many tables<br />
* [http://www.postgresql.org/message-id/flat/CAMkU%3D1wLjAsmJNuB6ZObZmGHqi9jLbK6n1eSgnOc5J1-AUsvUA@mail.gmail.com Thousands of schemas and ANALYZE goes out of memory]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce memory use when analyzing many tables in a single command by making catcache and syscache flushable or bounded.<br />
* [http://www.postgresql.org/message-id/flat/CAMkU%3D1yZnAYvMHENt8%3D9pgwE8q5zmX+mG%3DSXbFHiLkq_qn0B7Q@mail.gmail.com Thousands of schemas and ANALYZE goes out of memory]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== EXPLAIN ===<br />
{{TodoSubsection}}<br />
{{TodoItem<br />
|Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and actual row counts differ by a specified percentage}}<br />
<br />
{{TodoItem<br />
|Have EXPLAIN ANALYZE report rows as floating-point numbers<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg01363.php <nowiki>explain analyze rows=%.0f</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00108.php <nowiki>Re: explain analyze rows=%.0f</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Have EXPLAIN ANALYZE report buckets and memory usage for HashAggregate<br />
* [https://www.postgresql.org/message-id/flat/2527f5cb-5992-ae66-f3ec-4aa2396065ec%402ndquadrant.com <nowiki>to-do item for explain analyze of hash aggregates? </nowiki>]<br />
}}<br />
<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Window Functions ===<br />
See {{messageLink|357.1230492361@sss.pgh.pa.us|TODO items for window functions}}.<br />
{{TodoSubsection}}<br />
{{TodoItem<br />
|Support creation of user-defined window functions<br />
|We have the ability to create new window functions written in C. Is it<br />
worth the effort to create an API that would let them be written in PL/pgsql, etc?}}<br />
<br />
{{TodoItem<br />
|Investigate tuplestore performance issues<br />
|The tuplestore_in_memory() thing is just a band-aid, we ought to try to solve it properly. tuplestore_advance seems like a weak spot as well.<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg00152.php <nowiki>tuplestore potential performance problem</nowiki>]<br />
}}<br />
<br />
{{TodoItem|Do we really need so much duplicated code between Agg and WindowAgg?}}<br />
<br />
{{TodoItem<br />
|Teach planner to evaluate multiple windows in the optimal order<br />
|Currently windows are always evaluated in the query-specified order.<br />
* http://archives.postgresql.org/message-id/3CDAD71E9D70417290FCF66F0178D1E1@amd64<br />
}}<br />
<br />
{{TodoItem<br />
|Implement DISTINCT clause in window aggregates<br />
|Some proprietary RDBMSs have implemented it already, so it helps with porting from those.}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Integrity Constraints ==<br />
=== Keys ===<br />
<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Improve deferrable unique constraints for cases with many conflicts<br />
|The current implementation fires a trigger for each potentially conflicting row. This might not scale well for an update that changes many key values at once.<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Referential Integrity ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add MATCH PARTIAL referential integrity}}<br />
<br />
{{TodoItem<br />
|Change foreign key constraint for array -&gt; element to mean element in array?<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-10/msg01814.php <nowiki>foreign keys for array/period contains relationships</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix problem when cascading referential triggers make changes on cascaded tables, seeing the tables in an intermediate state<br />
* [http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php <nowiki>Re: [PATCHES] Work-in-progress referential action trigger timing</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Are ri_KeysEqual checks in the RI enforcement triggers still necessary?<br />
* [http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php <nowiki>Re: Effects of cascading references in foreign keys</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Check Constraints ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Run check constraints only when affected columns are changed<br />
* http://archives.postgresql.org/message-id/1326055327.15293.13.camel@vanquo.pezone.net<br />
}}<br />
<br />
{{TodoItem<br />
|Do not scan the table when a check constraint is added in the same command that adds the column<br />
* [http://www.postgresql.org/message-id/CAMkU%3D1z5vXZ8Txd9_8hvNFovtbGuP4VTitFRN59XDncEHVGtJA@mail.gmail.com skip table scan for adding column with provable check constraints]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Server-Side Languages ==<br />
<br />
{{TodoItem<br />
|Add support for polymorphic arguments and return types to languages other than PL/PgSQL}}<br />
<br />
{{TodoItem<br />
|Add support for OUT and INOUT parameters to languages other than PL/PgSQL}}<br />
<br />
{{TodoItem<br />
|Add more fine-grained specification of functions taking arbitrary data types<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg00367.php <nowiki>RfD: more powerful &quot;any&quot; types</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow holdable cursors in SPI}}<br />
<br />
{{TodoItem<br />
|Rethink query plan caching and timing of parse analysis within SQL-language functions<br />
|They should work more like plpgsql functions do ...<br />
* [http://archives.postgresql.org/pgsql-bugs/2011-05/msg00078.php <nowiki>Re: BUG #6019: invalid cached plan on inherited table</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow regex operations in PL/Perl using UTF8 characters in non-UTF8 encoded databases}}<br />
<br />
=== PL/pgSQL ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]}}<br />
<br />
{{TodoItem<br />
|<nowiki>Allow listing of record column names, and access to record columns via variables, e.g. columns := r.(*), tval2 := r.(colname)</nowiki><br />
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php <nowiki>Re: PL/PGSQL: Dynamic Record Introspection</nowiki>]<br />
* [http://pgxn.org/dist/colnames/ <nowiki>colnames: Extension to retrieve column names from a record</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow row and record variables to be set to NULL constants, and allow NULL tests on such variables<br />
|Because a row is not scalar, do not allow assignment from NULL-valued scalars.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php <nowiki>NULL and plpgsql rows</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider keeping separate cached copies when search_path changes<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php <nowiki>pl/pgsql Plan Invalidation and search_path</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve handling of NULL row values vs. NULL rows<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg01758.php <nowiki>Null row vs. row of nulls in plpgsql</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg01973.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve PERFORM handling of WITH queries or document limitation<br />
* http://archives.postgresql.org/pgsql-bugs/2011-03/msg00309.php<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== PL/Python ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Create a new restricted execution class that will allow passing function arguments in as locals. Passing them as globals means functions cannot be called recursively.<br />
* [http://archives.postgresql.org/pgsql-hackers/2011-02/msg01468.php <nowiki>Re: pl/python do not delete function arguments</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add a DB-API compliant interface on top of the SPI interface<br />
* http://petereisentraut.blogspot.com/2011/11/plpydbapi-db-api-for-plpython.html<br />
}}<br />
<br />
{{TodoItem<br />
|For functions returning a setof record with a composite type, cache the I/O functions for the composite type<br />
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg02007.php<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Clients ==<br />
<br />
{{TodoItem<br />
|Split out pg_resetxlog output into pre- and post-sections<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg02040.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve pg_rewind<br />
* [https://www.postgresql.org/message-id/CAN-RpxDhc_8JOq%3DcT9vd6MqWQaS0ZtvSf2LFV1V+bjOoEz02ow@mail.gmail.com Proposal: pg_rewind to skip config files]<br />
}}<br />
<br />
=== psql ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Move psql backslash database information into the backend, use mnemonic commands?<br />
|This would allow non-psql clients to pull the same information out of the database as psql. <br />
* [http://archives.postgresql.org/pgsql-hackers/2004-01/msg00191.php <nowiki>Re: psql \d option list overloaded</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Make psql's \d commands distinguish default privileges from no privileges<br />
|ACL displays were visibly different for the two cases before we "improved" them by using array_to_string.<br />
* [http://archives.postgresql.org/pgsql-bugs/2011-05/msg00082.php <nowiki>BUG #6021: There is no difference between default and empty access privileges with \dp</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consistently display privilege information for all objects in psql}}<br />
<br />
{{TodoItem<br />
|Add a \set variable to control whether \s displays line numbers<br />
|Another option is to add \# which lists line numbers, and allows command execution.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php <nowiki>Re: psql possible TODO</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Include the symbolic SQLSTATE name in verbose error reports<br />
* [http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php <nowiki>Re: Checking is TSearch2 query is valid</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add option to wrap column values at whitespace boundaries, rather than chopping them at a fixed width.<br />
|Currently, &quot;wrapped&quot; format chops values into fixed widths. Perhaps the word wrapping could use the same algorithm documented in the W3C specification. <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php <nowiki>Re: psql wrapped format default for backslash-d commands</nowiki>]<br />
* http://www.w3.org/TR/CSS21/tables.html#auto-table-layout}}<br />
<br />
{{TodoItem<br />
|Add option to print advice for people familiar with other databases<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-01/msg01845.php <nowiki>MySQL-ism help patch for psql</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix FETCH_COUNT to handle SELECT ... INTO and WITH queries<br />
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg01565.php<br />
* http://archives.postgresql.org/pgsql-bugs/2010-05/msg00192.php<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent psql from sending remaining single-line multi-statement queries after reconnecting<br />
* http://archives.postgresql.org/pgsql-bugs/2010-05/msg00159.php<br />
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg01283.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve line drawing characters<br />
* http://archives.postgresql.org/pgsql-hackers/2011-04/msg00386.php<br />
}}<br />
<br />
{{TodoItem<br />
|Consider improving the continuation prompt<br />
* http://archives.postgresql.org/pgsql-hackers/2011-04/msg01772.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve speed of tab completion by using LIKE<br />
* http://www.postgresql.org/message-id/20120821174847.GL1267@tamriel.snowman.net<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== pg_dump / pg_restore ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItemEasy<br />
|Dump security labels and comments on databases in a way that allows to load a dump into a differently named database<br />
* [http://www.postgresql.org/message-id/20150710115735.GH26521@alap3.anarazel.de security labels on databases are bad for dump & restore]<br />
|}}<br />
<br />
{{TodoItemEasy<br />
|<nowiki>Add full object name to the tag field. eg. for operators we need '=(integer, integer)', instead of just '='.</nowiki>}}<br />
<br />
{{TodoItem<br />
|Avoid using platform-dependent names for locales in pg_dumpall output<br />
|Using native locale names puts roadblocks in the way of porting a dump to another platform. One possible solution is to get<br />
CREATE DATABASE to accept some agreed-on set of locale names and fix them up to meet the platform's requirements.<br />
* http://archives.postgresql.org/message-id/21396.1241716688@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
|In a selective dump, allow dumping of an object and all its dependencies}}<br />
<br />
{{TodoItem<br />
|Stop dumping CASCADE on DROP TYPE commands in clean mode}}<br />
<br />
{{TodoItem<br />
|Allow pg_restore to load different parts of the COPY data for a single table simultaneously}}<br />
<br />
{{TodoItem<br />
|Preserve sparse storage of large objects over dump/restore<br />
* [http://archives.postgresql.org/message-id/18789.1349750451@sss.pgh.pa.us <nowiki>TODO item: teach pg_dump about sparsely-stored large objects</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent PL/pgSQL comment from throwing an error in a non-superuser restore<br />
* [http://www.postgresql.org/message-id/E1VuYH7-0008Rz-SV@wrigleys.postgresql.org Reloading dump fails at COMMENT ON EXTENSION plpgsql]<br />
}}<br />
<br />
{{TodoItem<br />
|Delay REFRESH MATERIALIZED VIEW until dependent indexes are created<br />
* [http://www.postgresql.org/message-id/20140820021530.2534.43156@wrigleys.postgresql.org pg_restore unusable for expensive matviews]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== pg_upgrade ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Handle large object comments<br />
|This is difficult to do because the large object doesn't exist when --schema-only is loaded.<br />
}}<br />
<br />
{{TodoItem<br />
|Consider using pg_depend for checking object usage in version.c<br />
}}<br />
<br />
{{TodoItem<br />
|Migrate pg_statistic by dumping it out as a flat file, so analyze is not necessary<br />
* [http://archives.postgresql.org/message-id/CAAZKuFaWdLkK8eozSAooZBets9y_mfo2HS6urPAKXEPbd-JLCA@mail.gmail.com pg_upgrade and statistics]<br />
* [https://www.postgresql.org/message-id/20171205140135.GA25023%40momjian.us Speeding up pg_upgrade]<br />
}}<br />
<br />
{{TodoItem<br />
|Find cleaner way to start/stop dedicated servers for upgrades<br />
* http://archives.postgresql.org/pgsql-hackers/2012-08/msg00275.php<br />
}}<br />
<br />
{{TodoItem<br />
|Desired changes that would prevent upgrades with pg_upgrade<br />
* 32-bit page checksums<br />
* Add metapage to GiST indexes<br />
* Clean up hstore's internal representation<br />
* Remove tuple infomask bit HEAP_MOVED_OFF and HEAP_MOVED_IN<br />
* [http://www.postgresql.org/message-id/CAK+WP1xdmyswEehMuetNztM4H199Z1w9KWRHVMKzyyFM+hV%3DzA@mail.gmail.com fix char() index trailing space handling]<br />
* [http://www.postgresql.org/message-id/CAPpHfdtxXMjyZxwND09ZLBBACVbWb5J9bLUf67CndR4VKFDgwg@mail.gmail.com Use non-collation-aware comparisons for GIN opclasses]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== ecpg ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Docs<br />
|Document differences between ecpg and the SQL standard and information about the Informix-compatibility module.}}<br />
<br />
{{TodoItem<br />
|Solve cardinality &gt; 1 for input descriptors / variables?}}<br />
<br />
{{TodoItem<br />
|Add a semantic check level, e.g. check if a table exists}}<br />
<br />
{{TodoItem<br />
|fix handling of DB attributes that are arrays}}<br />
<br />
{{TodoItem<br />
|Fix nested C comments}}<br />
<br />
{{TodoItemEasy<br />
|sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified}}<br />
<br />
{{TodoItem<br />
|Make SET CONNECTION thread-aware, non-standard?}}<br />
<br />
{{TodoItem<br />
|Allow multidimensional arrays}}<br />
<br />
{{TodoItem<br />
|Implement COPY FROM STDIN}} <br />
<br />
{{TodoItem<br />
|Provide a way to specify size of a bytea parameter<br />
* [http://archives.postgresql.org/message-id/200906192131.n5JLVoMo044178@wwwmaster.postgresql.org <nowiki>BUG #4866: ECPG and BYTEA</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow reuse of cursor name variables<br />
* [http://archives.postgresql.org/message-id/20100329113435.GA3430@feivel.credativ.lan <nowiki>Problems with variable cursorname in ecpg</nowiki>]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== libpq ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add PQexecf() that allows complex parameter substitution<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php <nowiki>Last minute mini-proposal (I know, know) for PQexecf()</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add SQLSTATE and severity to errors generated within libpq itself<br />
* [http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php <nowiki>v8.1: Error severity on libpq PGconn*</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01425.php<br />
}}<br />
<br />
{{TodoItem<br />
|Add support for interface/ipaddress binding to libpq<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg01811.php <nowiki>SR/libpq - outbound interface/ipaddress binding</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|When receiving a FATAL error remember it, so that it doesn't profess ingnorance about why the session was closed<br />
* [http://www.postgresql.org/message-id/CA+TgmoZ4P1cQetjOxQoHiG072UcE7dpE7dTBV8hMOidhwhof+g@mail.gmail.com<nowiki>Idle In Transaction Session Timeout, revived</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Pipelining support for libpq async API and an array-valued PQexecPrepared that uses it<br />
* [http://www.postgresql.org/message-id/CAMsr+YHE8Rt800yWcHEL8SrgruK0ng_nBmtKV6YMZ2BAzRBZzw@mail.gmail.com Foreign table batched inserts]<br />
}}<br />
{{TodoEndSubsection}}<br />
<br />
== Triggers ==<br />
<br />
{{TodoItem<br />
|Improve storage of deferred trigger queue<br />
|Right now all deferred trigger information is stored in backend memory. This could exhaust memory for very large trigger queues. This item involves dumping large queues into files, or doing some kind of join to process all the triggers, some bulk operation, or a bitmap. <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php <nowiki>Re: BUG #4204: COPY to table with FK has memory leak</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-10/msg00464.php <nowiki>Scaling up deferred unique checks and the after trigger queue</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2011-08/msg00023.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow triggers to be disabled in only the current session.<br />
|This is currently possible by starting a multi-statement transaction, modifying the system tables, performing the desired SQL, restoring the system tables, and committing the transaction. ALTER TABLE ... TRIGGER requires a table lock so it is not ideal for this usage.}}<br />
<br />
{{TodoItem<br />
|With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY<br />
|If the dump is known to be valid, allow foreign keys to be added without revalidating the data.}}<br />
<br />
{{TodoItem<br />
|When statement-level triggers are defined on a parent table, have them fire only on the parent table, and fire child table triggers only where appropriate<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg01883.php <nowiki>Statement-level triggers and inheritance</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Tighten trigger permission checks<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php <nowiki>Security leak with trigger functions?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow BEFORE INSERT triggers on views<br />
* [http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php <nowiki>Re: Why can't I put a BEFORE EACH ROW trigger on a view?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add database and transaction-level triggers<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php <nowiki>Proposal for db level triggers</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00620.php <nowiki>triggers on prepare, commit, rollback... ?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid requirement for AFTER trigger functions to return a value<br />
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg02384.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow creation of inline triggers<br />
* http://archives.postgresql.org/pgsql-hackers/2012-02/msg00708.php<br />
}}<br />
<br />
== Inheritance ==<br />
<br />
{{TodoItem<br />
|Allow unique indexes across inherited tables (requires multi-table indexes)<br />
* Postgres 11 allows unique indexes across partitions if the partition key is part of the index.<br />
}}<br />
<br />
{{TodoItem<br />
|Research whether ALTER TABLE / SET SCHEMA should work on inheritance hierarchies (and thus support ONLY)}}<br />
<br />
{{TodoItem<br />
|ALTER TABLE variants sometimes support recursion and sometimes not, but this is poorly/not documented, and the ONLY marker would then be silently ignored. Clarify the documentation, and reject ONLY if it is not supported.}}<br />
<br />
== Indexes ==<br />
<br />
{{TodoItem<br />
|Prevent index uniqueness checks when UPDATE does not modify the column<br />
|Uniqueness (index) checks are done when updating a column even if the column is not modified by the UPDATE.<br />
However, HOT already short-circuits this in common cases, so more work might not be helpful.<br />
* http://www.postgresql.org/message-id/CA+TgmoZOyaTanfEvNUdiHBCuu9Zh0JVP1e_UTVbx6Rvj9vFC9Q@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Consider having a larger statistics target for indexed columns and expression indexes. <br />
}}<br />
<br />
{{TodoItem<br />
|Allow multiple indexes to be created concurrently, ideally via a single heap scan<br />
|pg_restore allows parallel index builds, but it is done via subprocesses, and there is no SQL interface for this.<br />
Cluster could definitely benefit from this.<br />
* http://archives.postgresql.org/pgsql-performance/2011-04/msg00093.php<br />
* http://www.postgresql.org/message-id/CADVWZZJ5AS%3DXVrDwfTQqQP_V1+_fTYcZhq%3Dd5CbCXoALCjObbg@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Consider sorting entries before inserting into btree index<br />
* [http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php <nowiki>Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider using "effective_io_concurrency" for index scans<br />
|Currently only bitmap scans use this, which might be fine because most multi-row index scans use bitmap scans.<br />
* [http://www.postgresql.org/message-id/CAGTBQpZzf70n0PYJ%3DVQLd+jb3wJGo%3D2TXmY+SkJD6G_vjC5QNg@mail.gmail.com Prefetch index pages for B-Tree index scans]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow GIN indexes to be used for exclusion constraints<br />
* http://archives.postgresql.org/pgsql-hackers/2012-05/msg00669.php<br />
}}<br />
<br />
{{TodoItem<br />
| Allow "loose" or "skip" scans on btree indexes in which the first column has low cardinality<br />
* http://archives.postgresql.org/pgsql-performance/2012-08/msg00159.php<br />
}}<br />
<br />
{{TodoItem<br />
| Make the planner's "special index operator" mechanism extensible<br />
* http://www.postgresql.org/message-id/27270.1364700924@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
| Allow index-only COUNT(*) for indexes which don't support index-only scans<br />
}}<br />
<br />
{{TodoItem<br />
|Improve GIN performance<br />
* [http://www.postgresql.org/message-id/52F373CC.4050800@vmware.com Small GIN optimizations (after 9.4)]<br />
}}<br />
<br />
{{TodoItem<br />
| Teach GIN cost estimation about "fast scans"<br />
* http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com<br />
}}<br />
<br />
{{TodoItem<br />
| Allow unlogged indexes<br />
* http://www.postgresql.org/message-id/11561.1414793261@sss.pgh.pa.us<br />
}}<br />
<br />
=== GIST ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add more GIST index support for geometric data types}}<br />
<br />
{{TodoItem<br />
|Allow GIST indexes to create more complex index types, like digital trees (see Aoki)}}<br />
<br />
{{TodoItem<br />
|Fix performance issues in contrib/seg and contrib/cube GiST support<br />
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904161633160.4053@aragorn.flymine.org GiST index performance]<br />
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904221704470.22330@aragorn.flymine.org draft patch]<br />
* [http://archives.postgresql.org/pgsql-performance/2009-05/msg00069.php <nowiki>Re: GiST index performance</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-performance/2009-06/msg00068.php <nowiki>GiST index performance</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|[http://archives.postgresql.org/message-id/4DC8D284-05CF-4E3D-9670-AC9A32C37A36@justatheory.com GiST index support for arrays]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Hash ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Add UNIQUE capability to hash indexes<br />
* [https://www.postgresql.org/message-id/592254A5.9000809@anastigmatix.net Re: PG10 Crash-safe and replicable Hash Indexes and UNIQUE]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow multi-column hash indexes<br />
* This requires all columns to be specified for a query to use the index.<br />
* [https://www.postgresql.org/message-id/CA+Tgmoax6DhnKsuE_gzY5qkvmPEok77JAP1h8wOTbf+dg2Ycrw@mail.gmail.com Write Ahead Logging for Hash Indexes]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Sorting ==<br />
<br />
{{TodoItem<br />
|Consider detoasting keys before sorting}}<br />
<br />
{{TodoItem<br />
|Allow sorts of skinny tuples to use even more available memory.<br />
|Now that it is not limited by MaxAllocSize, don't limit by INT_MAX either.<br />
* [http://www.postgresql.org/message-id/CA+U5nMKkRMin1pV8VMpS6_n7hcOWSG0kZS3oFL9JOa8DV6vJyQ@mail.gmail.com Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize]<br />
}}<br />
<br />
== Cache Usage ==<br />
<br />
{{TodoItem<br />
|Consider automatic caching of statements at various levels:<br />
* Parsed query tree<br />
* Query execute plan<br />
* Query results <br />
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php <nowiki>Cached Query Plans (was: global prepared statements)</nowiki>]<br />
* [https://www.postgresql.org/message-id/CAFj8pRAGLaiEm8ur5DWEBo7qHRWTk9HxkuUAz00CZZtJj-LkCA%40mail.gmail.com PoC plpgsql - possibility to force custom or generic plan]<br />
* [https://www.postgresql.org/message-id/CADT4RqAd_74m6MUbXAPsYzqXG3F6wWVhS_dFJijrfXs7N+QGHQ@mail.gmail.com Cached/global query plans, autopreparation]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider allowing higher priority queries to have referenced shared buffer pages stay in memory longer<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php <nowiki>Re: How to keep a table in memory?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix memory leak caused by negative catcache entries<br />
* [http://www.postgresql.org/message-id/51C0A1FF.2050404@vmware.com <nowiki>Re: Memory leak in PL/pgSQL function which CREATE/SELECT/DROP a temporary table</nowiki>]<br />
* [https://www.postgresql.org/message-id/flat/20161219.201505.11562604.horiguchi.kyotaro@lab.ntt.co.jp <nowiki>Protect syscache from bloating with negative cache entries</nowiki>]<br />
}}<br />
<br />
== Vacuum ==<br />
<br />
{{TodoItem<br />
|Consider having single-page pruning update the visibility map<br />
* <nowiki>https://commitfest.postgresql.org/action/patch_view?id=75</nowiki><br />
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg02344.php <nowiki>Re: visibility maps and heap_prune</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow VACUUM FULL and CLUSTER to update the visibility map<br />
* https://www.postgresql.org/message-id/CAPpHfdtcxUVys6r6JqX2s%2B5CowXDKMOnfcJoJWHyjWDe%3DhwHMw%40mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Improve tracking of total relation tuple counts now that vacuum doesn't always scan the whole heap<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00531.php Partial vacuum versus pg_class.reltuples]<br />
}}<br />
<br />
{{TodoItem<br />
|Bias FSM towards returning free space near the beginning of the heap file, in hopes that empty pages at the end can be truncated by VACUUM<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg01124.php <nowiki>FSM search modes</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add a way to compact tables without exclusive locking, similar to pre-9.0 VACUUM FULL<br />
* [http://www.postgresql.org/message-id/20150424190403.GP4369@alvh.no-ip.org Re: Feedback on getting rid of VACUUM FULL]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider a more compact data representation for dead tuple locations within VACUUM<br />
* https://www.postgresql.org/message-id/flat/CAD21AoAfOZvmfR0j8VmZorZjL7RhTiQdVttNuC4W-Shdc2a-AA%40mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Provide more information in order to improve user-side estimates of dead space bloat in relations<br />
* [http://archives.postgresql.org/pgsql-general/2009-05/msg01039.php <nowiki>Re: Bloated Table</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce the number of table scans performed by vacuum<br />
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg01119.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg00624.php<br />
}}<br />
<br />
{{TodoItem<br />
|Vacuum Gin indexes in physically order rather than logical order<br />
* http://archives.postgresql.org/pgsql-hackers/2012-04/msg00443.php<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid creation of the free space map for small tables<br />
* http://archives.postgresql.org/pgsql-hackers/2011-11/msg01751.php<br />
}}<br />
<br />
=== Auto-vacuum ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Issue log message to suggest VACUUM FULL if a table is nearly empty?<br />
*[http://www.postgresql.org/message-id/F40B0968DB0A904DA78A924E633BE78645FAAF@SYDEXCHTMP2.au.fjanz.com discussion]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent long-lived temporary tables from causing frozen-xid advancement starvation<br />
|The problem is that autovacuum cannot vacuum them to set frozen xids; only the session that created them can. <br />
* [http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php <nowiki>Re: AutoVacuum Behaviour Question</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Prevent autovacuum from running if an old transaction is still running from the last vacuum<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php <nowiki>Re: Autovacuum and OldestXmin</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Have autoanalyze of parent tables occur when child tables are modified<br />
* http://archives.postgresql.org/pgsql-performance/2010-06/msg00137.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow visibility map all-visible bits to be set even when an auto-ANALYZE is running<br />
* http://archives.postgresql.org/pgsql-hackers/2012-01/msg00356.php<br />
}}<br />
<br />
{{TodoItem<br />
|Improve autoanalyze thresholds for small tables<br />
* http://www.postgresql.org/message-id/5078AD6B.8060802@agliodbs.com<br />
}}<br />
<br />
{{TodoItem<br />
|Make autovacuum scheduling smarter<br />
* https://www.postgresql.org/message-id/0A3221C70F24FB45833433255569204D1F8A4DC6%40G01JPEXMBYT05<br />
* https://www.postgresql.org/message-id/CAD21AoBUaSRBypA6pd9ZD%3DU-2TJCHtbyZRmrS91Nq0eVQ0B3BA%40mail.gmail.com<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Locking ==<br />
<br />
{{TodoItem<br />
|Fix problem when multiple subtransactions of the same outer transaction hold different types of locks, and one subtransaction aborts<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php <nowiki>FOR SHARE vs FOR UPDATE locks</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php <nowiki>Re: FOR SHARE vs FOR UPDATE locks</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php <nowiki>Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php <nowiki>Re: savepoints and upgrading locks</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve deadlock detection when a page cleaning lock conflicts with a shared buffer that is pinned<br />
* [http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php <nowiki>BUG #3883: Autovacuum deadlock with truncate?</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php <nowiki>Thoughts about bug #3883</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php <nowiki>Re: pgsql: Add checks to TRUNCATE, CLUSTER, and REINDEX to prevent</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Detect deadlocks involving LockBufferForCleanup()<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php <nowiki>Thoughts about bug #3883</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow finer control over who is cancelled in a deadlock<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01727.php<br />
}}<br />
<br />
== Startup Time Improvements ==<br />
<br />
{{TodoItem<br />
|Allow backends to change their database without restart<br />
|This allows for faster server startup.<br />
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg00843.php<br />
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg00336.php<br />
}}<br />
<br />
== Write-Ahead Log ==<br />
<br />
{{TodoItem<br />
|Eliminate need to write full pages to WAL before page modification<br />
|Currently, to protect against partial disk page writes, we write full page images to WAL before they are modified so we can correct any partial page writes during recovery. These pages can also be eliminated from point-in-time archive files. <br />
* [http://archives.postgresql.org/pgsql-hackers/2002-06/msg00655.php <nowiki>Re: Index Scans become Seq Scans after VACUUM ANALYSE</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg01191.php<br />
* [http://archives.postgresql.org/message-id/20120105061916.GB21048@fetter.org WIP double writes]<br />
* [http://archives.postgresql.org/message-id/4EFC449F02000025000441CD@gw.wicourts.gov double writes]<br />
* [http://archives.postgresql.org/message-id/20120110214344.GB21106@fetter.org Double-write with Fast Checksums]<br />
* [http://archives.postgresql.org/message-id/1962493974.656458.1327703514780.JavaMail.root@zimbra-prod-mbox-4.vmware.com double writes using "double-write buffer" approach]<br />
* http://archives.postgresql.org/pgsql-hackers/2012-10/msg01463.php<br />
}}<br />
<br />
{{TodoItem<br />
|When full page writes are off, write CRC to WAL and check file system blocks on recovery<br />
|If CRC check fails during recovery, remember the page in case a later CRC for that page properly matches. The difficulty is that hint bits are not WAL logged, meaning a valid page might not match the earlier CRC.}}<br />
<br />
{{TodoItem<br />
|Write full pages during file system write and not when the page is modified in the buffer cache<br />
|This allows most full page writes to happen in the background writer. It might cause problems for applying WAL on recovery into a partially-written page, but later the full page will be replaced from WAL.<br />
* [http://archives.postgresql.org/message-id/CAGvK12UST-tPhyLrSLuSpwFxZbAO79yYrhV2xaLmS2MkUxNUVQ@mail.gmail.com Page Checksums + Double Writes]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow WAL information to recover corrupted pg_controldata<br />
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php <nowiki>Re: [HACKERS] pg_resetxlog -r flag</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Speed WAL recovery by allowing more than one page to be prefetched<br />
|This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay. <br />
* [http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php <nowiki>Slow PITR restore</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php <nowiki>Re: [GENERAL] Slow PITR restore</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php <nowiki>Read-ahead and parallelism in redo recovery</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve WAL concurrency by increasing lock granularity<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php <nowiki>Reworking WAL locking</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Have resource managers report the duration of their status changes<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php <nowiki>Recovery of Multi-stage WAL actions</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Close deleted WAL files held open in *nix by long-lived read-only backends<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php <nowiki>Deleted WAL files held open by backends in Linux</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php <nowiki>Re: Deleted WAL files held open by backends in Linux</nowiki>]<br />
}}<br />
<br />
== Optimizer / Executor ==<br />
<br />
{{TodoItem<br />
|Improve selectivity functions for geometric operators}}<br />
<br />
{{TodoItem<br />
|Consider adding a useful and convenient way of seeing paths rejected by the planner. OPTIMIZER_DEBUG does this so some extent but it seemingly gets very little use and must be enabled during compilation.<br />
* http://archives.postgresql.org/pgsql-hackers/2012-08/msg00597.php<br />
* https://postgr.es/m/1fd8e494-4740-4108-6d06-d5a173836047@gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Log statements where the optimizer row estimates were dramatically different from the number of rows actually found?}}<br />
<br />
{{TodoItem<br />
|Consider compressed annealing to search for query plans<br />
|This might replace GEQO.<br />
* http://archives.postgresql.org/message-id/15658.1241278636%40sss.pgh.pa.us<br />
}}<br />
<br />
=== Hashing ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Allow single batch hash joins to preserve outer pathkeys<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg00806.php Re: Potential Join Performance Issue]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid building the same hash table more than once during the same query<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid hashing for distinct and then re-hashing for hash join<br />
* [http://archives.postgresql.org/message-id/4136ffa0902191346g62081081v8607f0b92c206f0a@mail.gmail.com Re: Fixing Grittner's planner issues]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Background Writer ==<br />
<br />
{{TodoItem<br />
|Consider having the background writer update the transaction status hint bits before writing out the page<br />
|Implementing this requires the background writer to have access to system catalogs and the transaction status log.<br />
* [http://www.postgresql.org/message-id/CAMkU%3D1zf1Yo0dYJzJ-pk9o4mwLuMD4Uzw6Jck7u1nC_Xb2gYWA@mail.gmail.com Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider adding buffers the background writer finds reusable to the free list <br />
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php <nowiki>Background LRU Writer/free list</nowiki>]<br />
* [http://archives.postgresql.org/message-id/CA+U5nMKtvyDcV4zTr7bq7t6cA2nBfLxCJ8tQgVBnc5ddRPO+Bg@mail.gmail.com our buffer replacement strategy is kind of lame]<br />
* [http://www.postgresql.org/message-id/CAOeZVic4HikhmzVD%3DZP4JY9g8PgpyiQQOXOELWP%3DkR+%3DH1Frgg@mail.gmail.com Page replacement algorithm in buffer cache]<br />
* [http://www.postgresql.org/message-id/002f01ce50a8$e057c7a0$a10756e0$@kapila@huawei.com Move unused buffers to freelist]<br />
}}<br />
<br />
{{TodoItem<br />
|Automatically tune bgwriter_delay based on activity rather then using a fixed interval<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php <nowiki>Background LRU Writer/free list</nowiki>]<br />
* [http://archives.postgresql.org/message-id/CA+U5nMKtvyDcV4zTr7bq7t6cA2nBfLxCJ8tQgVBnc5ddRPO+Bg@mail.gmail.com our buffer replacement strategy is kind of lame]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider whether increasing BM_MAX_USAGE_COUNT improves performance<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php <nowiki>Bgwriter LRU cleaning: we've been going at this all wrong</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency<br />
* [http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php <nowiki>Re: Load Distributed Checkpoints, final patch</nowiki>]<br />
}}<br />
<br />
== Concurrent Use of Resources ==<br />
<br />
{{TodoItem<br />
|Do async I/O for faster random read-ahead of data<br />
|Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php <nowiki>Asynchronous I/O Support</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php <nowiki>Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php <nowiki>There's random access and then there's random access</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php <nowiki>Bitmap index scan preread using posix_fadvise (Was: There's random access and then there's random access)</nowiki>]<br />
The above patch is already applied as of 8.4, but it still remains to figure out how to handle plain indexscans effectively.<br />
* [http://archives.postgresql.org//pgsql-hackers/2009-01/msg00806.php Problems with the patch submitted for posix_fadvise in index scans]<br />
}}<br />
<br />
{{TodoItem<br />
|SMP scalability improvements<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php <nowiki>Straightforward changes for increased SMP scalability</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php <nowiki>Re: Reducing Transaction Start/End Contention</nowiki>]<br />
}}<br />
<br />
== TOAST ==<br />
<br />
{{TodoItem<br />
|Allow user configuration of TOAST thresholds<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php <nowiki>Re: Proposed adjustments in MaxTupleSize and toastthresholds</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php <nowiki>pg_lzcompress strategy parameters</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce unnecessary cases of deTOASTing<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php <nowiki>Re: [PATCHES] Eliminate more detoast copies for packed varlenas</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce costs of repeat de-TOASTing of values<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg01096.php <nowiki>WIP patch: reducing overhead for repeat de-TOASTing</nowiki>]<br />
}}<br />
<br />
== Monitoring ==<br />
<br />
{{TodoItem<br />
|Have pg_stat_activity display query strings in the correct client encoding<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-01/msg00131.php <nowiki>pg_stats queries versus per-database encodings</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
| Allow reporting of stalls due to wal_buffer wrap-around<br />
* http://archives.postgresql.org/pgsql-hackers/2012-02/msg00826.php<br />
}}<br />
<br />
{{TodoItem<br />
| Restructure pg_stat_database columns tup_returned and tup_fetched to return meaningful values<br />
* http://www.postgresql.org/message-id/20121012060345.GA29214@toroid.org<br />
}}<br />
<br />
{{TodoItem<br />
| Improve handling of pg_stat_statements handling of bind "IN" variables<br />
* [http://www.postgresql.org/message-id/CAM3SWZSpdPB3uErnXWMt3q74y0r+84ZsOt2U3HKKes_V7O+0Qg@mail.gmail.com Revisiting pg_stat_statements and IN()]<br />
}}<br />
<br />
== Miscellaneous Performance ==<br />
<br />
{{TodoItem<br />
|Rather than consider mmap()-ing in 8k pages, consider mmap()'ing entire files into a backend?<br />
|Doing I/O to large tables would consume a lot of address space or require frequent mapping/unmapping. Extending the file also causes mapping problems that might require mapping only individual pages, leading to thousands of mappings. Another problem is that there is no way to _prevent_ I/O to disk from the dirty shared buffers so changes could hit disk before WAL is written.<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01239.php<br />
}}<br />
<br />
{{TodoItem<br />
|Allow configuration of backend priorities via the operating system<br />
|Though backend priorities make priority inversion during lock waits possible, research shows that this is not a huge problem.<br />
* [http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php <nowiki>Priorities for users or queries?</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider if CommandCounterIncrement() can avoid its AcceptInvalidationMessages() call<br />
* [http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php <nowiki>pgsql: Avoid incrementing the CommandCounter when</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider Cartesian joins when both relations are needed to form an indexscan qualification for a third relation<br />
* [http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php <nowiki>Re: TB-sized databases</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider not storing a NULL bitmap on disk if all the NULLs are trailing<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php <nowiki>Proposal for Null Bitmap Optimization(for Trailing NULLs)</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php <nowiki>Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Sort large UPDATE/DELETEs so it is done in heap order<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php <nowiki>Possible future performance improvement: sort updates/deletes by ctid</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add auto-tuning of work_mem<br />
* [http://www.postgresql.org/message-id/20131009143046.GT22450@momjian.us Auto-tuning work_mem and maintenance_work_mem]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider decreasing the I/O caused by updating tuple hint bits<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00847.php <nowiki>Hint Bits and Write I/O</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-07/msg00199.php <nowiki>Re: [HACKERS] Hint Bits and Write I/O</nowiki>]<br />
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg00695.php<br />
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg00792.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-01/msg01063.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01408.php<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01453.php<br />
}}<br />
<br />
{{TodoItem<br />
|Avoid reading in b-tree pages when replaying vacuum records in hot standby mode<br />
* [http://archives.postgresql.org/message-id/1272571938.4161.14739.camel@ebony <nowiki>Hot Standby tuning for btree_xlog_vacuum()</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Restructure truncation logic to be more resistant to failure<br />
|This also involves not writing dirty buffers for a truncated or dropped relation<br />
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01032.php<br />
}}<br />
<br />
{{TodoItem<br />
|Enhance foreign data wrappers, parallelism, partitioning, and perhaps add a global snapshot/transaction manager to allow creation of a proof-of-concept built-in sharding solution<br />
|Ideally these enhancements and new facilities will be available to external sharding solutions as well.<br />
* [https://wiki.postgresql.org/wiki/Built-in_Sharding Built-in sharding wiki]<br />
}}<br />
<br />
== Miscellaneous Other ==<br />
<br />
{{TodoItem<br />
|Deal with encoding issues for filenames in the server filesystem<br />
* {{MessageLink|20090413184335.39BE.52131E4D@oss.ntt.co.jp|a proposed patch here}}<br />
* {{MessageLink|8484.1244655656@sss.pgh.pa.us|some issues about it here}}<br />
* {{MessageLink|20100107103740.97A5.52131E4D@oss.ntt.co.jp|Windows-specific patch here}}<br />
}}<br />
<br />
{{TodoItem<br />
|Deal with encoding issues in the output of localeconv()<br />
* [http://archives.postgresql.org/message-id/40c6d9160904210658y590377cfw6dbbecb53d2b8be0@mail.gmail.com bug report]<br />
* [http://archives.postgresql.org/message-id/49EF8DA0.90008@tpf.co.jp draft patch]<br />
* [http://archives.postgresql.org/message-id/21710.1243620986@sss.pgh.pa.us review of patch]<br />
}}<br />
<br />
{{TodoItem<br />
|Provide schema name and other fields available from SQL GET DIAGNOSTICS in error reports<br />
* [http://archives.postgresql.org/message-id/dcc563d10810211907n3c59a920ia9eb7cd2a6d5ea58@mail.gmail.com <nowiki>How to get schema name which violates fk constraint</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg00846.php <nowiki>patch - Report the schema along table name in a referential failure error message</nowiki>]<br />
* {{MessageLink|3191.1263306359@sss.pgh.pa.us|Re: NOT NULL violation and error-message}}<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-08/msg00213.php <nowiki>the case for machine-readable error fields</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Use sa_mask to close race conditions between signal handlers<br />
* http://www.postgresql.org/message-id/20130911013107.GA225735@tornado.leadboat.com<br />
}}<br />
<br />
{{TodoItem<br />
|Allow pg_export_snapshot() to run on hot standby servers<br />
|This will allow parallel pg_dump on such servers.<br />
* [http://www.postgresql.org/message-id/CA+U5nML2VMJ3R2YBAZ+CsAsTWF3LuYSo16Wu9+yXFrfy4%3Df2fA@mail.gmail.com pg_export_snapshot on standby side]<br />
}}<br />
<br />
{{TodoItem<br />
|Provide a way to enumerate and unregister background workers<br />
|Right now the only way to unregister bgworkers is from within the worker with <tt>proc_exit(0)</tt> or registering with <tt>BGW_NEVER_RESTART</tt><br />
* https://www.postgresql.org/message-id/CAMsr%2BYG-fD%2BmP-BNZDheVYucC7%3DoUn8ByTQSFz7RKkVX2MRS2Q%40mail.gmail.com<br />
}}<br />
<br />
== Source Code ==<br />
<br />
{{TodoItem<br />
|Rationalize division of labor between initdb and bootstrap<br />
* [https://www.postgresql.org/message-id/20220216021219.ygzrtb3hd5bn7olz%40alap3.anarazel.de <nowiki>initdb / bootstrap design</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow cross-compiling by generating the zic database on the target system}}<br />
<br />
{{TodoItem<br />
|Improve NLS maintenance of libpgport messages linked onto applications}}<br />
<br />
{{TodoItem<br />
|Use UTF8 encoding for NLS messages so all server encodings can read them properly}}<br />
<br />
{{TodoItem<br />
|Allow creation of universal binaries for Darwin<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00884.php <nowiki>Getting to universal binaries for Darwin</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider GnuTLS if OpenSSL license becomes a problem<br />
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg00892.php<br />
* [http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php <nowiki>[PATCH] Add support for GnuTLS</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php <nowiki>TODO: GNU TLS</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider making NAMEDATALEN more configurable<br />
|There is demand for making 128 the default, but there are also concerns about storage and memory usage and performance. So a rearchitecting to make the storage variable-length might be preferred.<br />
* Discussions when it was changed from 32 to 64: [https://www.postgresql.org/message-id/flat/003901c1b4ca%241d762500%248001a8c0%40jester] [https://www.postgresql.org/message-id/flat/1019615774.84994.11.camel%40knight.zort.ca] [https://www.postgresql.org/message-id/flat/D90A5A6C612A39408103E6ECDD77B82920CE98%40voyager.corporate.connx.com] [https://www.postgresql.org/message-id/flat/01C273A8.DA59BF90.jochen.westland%40invigo.de]<br />
* [https://www.postgresql.org/message-id/flat/1499106661641-5969858.post%40n3.nabble.com <nowiki>Revisiting NAMEDATALEN</nowiki>]<br />
* [https://www.postgresql.org/message-id/flat/CALSd-crdmj9PGdvdioU%3Da5W7P%3DTgNmEB2QP9wiF6DTUbBuMXrQ%40mail.gmail.com <nowiki>NAMEDATALEN increase because of non-latin languages</nowiki>] (contains ideas about variable-length storage)<br />
}}<br />
<br />
{{TodoItem<br />
|Research use of signals and sleep wake ups<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php <nowiki>Restartable signals 'n all that</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider simplifying how memory context resets handle child contexts<br />
* [http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php <nowiki>Re: Memory leak in nodeAgg</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Implement the non-threaded Avahi service discovery protocol<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00939.php <nowiki>Re: [PATCHES] Avahi support for Postgresql</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00097.php <nowiki>Re: Avahi support for Postgresql</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg01211.php <nowiki>Re: [PATCHES] Avahi support for Postgresql</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-04/msg00001.php <nowiki>Re: [HACKERS] Avahi support for Postgresql</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce data row alignment requirements on some 64-bit systems<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00369.php <nowiki>[WIP] Reduce alignment requirements on 64-bit systems.</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Restructure TOAST internal storage format for greater flexibility<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg00049.php <nowiki>Re: PG_PAGE_LAYOUT_VERSION 5 - time for change</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
| Consider removing the attribute options cache<br />
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg00039.php<br />
}}<br />
<br />
{{TodoItem<br />
| Restructure /contrib section<br />
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg00705.php<br />
}}<br />
<br />
=== Windows ===<br />
{{TodoSubsection}}<br />
<br />
{{TodoItem<br />
|Remove configure.in check for link failure when the cause is found}}<br />
<br />
{{TodoItem<br />
|Allow psql to use readline once non-US code pages work with backslashes}}<br />
<br />
{{TodoItem<br />
|Improve signal handling<br />
* [http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php <nowiki>Simplify Win32 Signaling code</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Support PGXS when using MSVC}}<br />
<br />
{{TodoItem<br />
|Fix MSVC NLS support, like for to_char()<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php <nowiki>NLS on MSVC strikes back!</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php <nowiki>Fix for 8.3 MSVC locale (Was [HACKERS] NLS on MSVC strikes back!)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Fix global namespace issues when using multiple terminal server sessions<br />
* [http://archives.postgresql.org/message-id/48F3BFCC.8030107@dunslane.net problems with Windows global namespace]}}<br />
<br />
{{TodoItem<br />
|Change from the current autoconf/gmake build system to cmake<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg01869.php <nowiki>About CMake (was Re: [COMMITTERS] pgsql: Append major version number and for libraries soname major)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Improve consistency of path separator usage<br />
* http://archives.postgresql.org/message-id/49C0BDC5.4010002@hagander.net<br />
}}<br />
<br />
{{TodoItem<br />
|Fix cross-compiling on Windows<br />
* http://archives.postgresql.org/pgsql-bugs/2010-10/msg00110.php<br />
}}<br />
<br />
{{TodoItem<br />
|Reduce file statistics overhead on directory reads<br />
* http://www.postgresql.org/message-id/1338325561.82125.YahooMailNeo@web39304.mail.mud.yahoo.com<br />
}}<br />
<br />
{{TodoItem<br />
|Fix hang with long file paths<br />
* [http://www.postgresql.org/message-id/CAA4eK1JxaBofxpcgLqCx9EB%3Dm3PaXr9iFU9%3DV3ddDswsPZooxw@mail.gmail.com Long paths for tablespace leads to uninterruptible hang in Windows]<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
=== Wire Protocol Changes / v4 Protocol ===<br />
{{TodoSubsection}}<br />
<br />
<br />
{{TodoItem<br />
|Allow dynamic character set handling}}<br />
<br />
{{TodoItem<br />
|Ensure the client can determine the encoding of messages sent early in the handshake<br />
* http://www.postgresql.org/message-id/541A5659.5050006@2ndquadrant.com}}<br />
<br />
{{TodoItem<br />
|Let the client indicate character encoding of database names, user names, passwords, and of pre-auth error messages returned by the server<br />
* http://www.postgresql.org/message-id/16160.1360540050@sss.pgh.pa.us<br />
* http://www.postgresql.org/message-id/20131220030725.GA1411150@tornado.leadboat.com<br />
}}<br />
<br />
{{TodoItem<br />
|Send numeric version to clients in fixed header<br />
* [https://commitfest.postgresql.org/10/752/ <nowiki>patch to send server_version_num in v3 protocol as GUC_REPORT</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Add decoded type length/precision (i.e. typmod information)}}<br />
<br />
{{TodoItem<br />
|Mark result columns as known-not-null when possible<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-11/msg01029.php <nowiki>Adding nullable indicator to Describe</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Use compression<br />
|Specify and implement wire protocol compression. If SSL transparent compression is used, hopefully avoid the overhead of key negotiation and encryption when SSL is configured only for compression. Note that [https://www.ietf.org/mail-archive/web/tls/current/msg11619.html compression is being removed from TLS 1.3] so we really need to do it ourselves.<br />
* http://archives.postgresql.org/pgsql-hackers/2012-06/msg00793.php<br />
}}<br />
<br />
{{TodoItem<br />
|Update clients to use data types, typmod, schema.table.column names of result sets using new statement protocol}}<br />
<br />
{{TodoItem<br />
|Set protocol for wire format negotiation<br />
* [http://archives.postgresql.org/message-id/CACMqXCKkGrGXxQhjHCKCe0B8hn6sTt-1sdgHZOSGQMxrusOsQA@mail.gmail.com GUC_REPORT for protocol tunables]<br />
}}<br />
<br />
{{TodoItem<br />
|Make sure upgrading to a 4.1 protocol version will actually work smoothly<br />
* [http://archives.postgresql.org/message-id/28307.1318255008@sss.pgh.pa.us Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable]<br />
}}<br />
<br />
{{TodoItem<br />
|Allow multi-state authentication (e.g. try client peer, fall back to md5)<br />
* http://www.postgresql.org/message-id/51A44185.5060306@2ndquadrant.com<br />
* http://www.postgresql.org/message-id/55192AFE.6080106@iki.fi<br />
* http://www.postgresql.org/message-id/54DB1D4E.8090700@vmware.com<br />
* https://commitfest.postgresql.org/6/320/<br />
}}<br />
<br />
{{TodoItem<br />
|Allow re-authentication<br />
|Let the client request re-authentication as a different user mid session, for connection pools that pass through the handshake.<br />
}}<br />
<br />
{{TodoItem<br />
|Identify the affected object in CommandComplete message?<br />
* http://www.postgresql.org/message-id/CAAfz9KNGVoyM+z_2tnPKTDXG_RdR9a33Y5s+zQ9LdwTTsqqZng@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Allow negotiation of encryption, <tt>STARTTLS</tt> style, rather than forcing client to decide on SSL or !SSL before connecting<br />
* http://www.postgresql.org/message-id/5406EAD3.7070002@2ndquadrant.com}}<br />
<br />
{{TodoItem<br />
|Permit lazy fetches of large values, at least out-of-line TOASTED values<br />
* http://www.postgresql.org/message-id/53FF0EF8.100@2ndquadrant.com<br />
}}<br />
<br />
{{TodoItem<br />
|Add session-level whitelisting of types for binary-mode transfer<br />
* http://www.postgresql.org/message-id/30470.1412055068@sss.pgh.pa.us<br />
}}<br />
<br />
{{TodoItem<br />
|Send client the xid when it is allocated<br />
|Lets the client later ask the server "did this commit or not?" after interterminate result due to crash or connection loss<br />
}}<br />
<br />
{{TodoItem<br />
|Report xlog position in commit message<br />
|Help enable client-side failover by providing a token clients can use to see if a commit has replayed to replicas yet<br />
* http://www.postgresql.org/message-id/53E2D346.9030806@2ndquadrant.com<br />
}}<br />
<br />
{{TodoItem<br />
|Changes to make cancellations more reliable and more secure<br />
* http://www.postgresql.org/message-id/CADT4RqAUd7wYYsM9D7GHJnZj3J79D4W%3Dved2kqM5mVt5cuGHgg@mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|Clarify semantics of statement_timeout in extended query protocol<br />
|Batched and pipelined queries have unexpected behaviour with statement_timeout. Client needs to be able to specify statement boundary with protocol message.<br />
* https://www.postgresql.org/message-id/20160528.220442.1489791680347556026.t-ishii@sraoss.co.jp<br />
}}<br />
<br />
{{TodoItem<br />
|Create a more efficient way to handle out-of-line parameters<br />
* [https://www.postgresql.org/message-id/12500.1470002232%40sss.pgh.pa.us Re: Slowness of extended protocol]<br />
}}<br />
<br />
{{TodoItem<br />
|Separate transaction delineation from protocol error recovery (in v3 both are managed via the same Sync message)<br />
* https://www.postgresql.org/message-id/CADT4RqDdo9EcFbxwB_YO2H3BVZ0t-1qqZ%3D%2B%2BdVMnYaN6BpyUGQ%40mail.gmail.com<br />
* https://www.postgresql.org/message-id/CAMsr%2BYEgnJ8ZAWPLx5%3DBCbYYq9SNTdwbwvUcb7V-vYm5d5uhbQ%40mail.gmail.com<br />
}}<br />
<br />
{{TodoEndSubsection}}<br />
<br />
== Documentation ==<br />
<br />
{{TodoItem<br />
|Provide a manpage for postgresql.conf<br />
* {{messageLink|20080819194311.GH4428@alvh.no-ip.org|A smaller default postgresql.conf}}<br />
* {{messageLink|200808211910.37524.peter_e@gmx.net|A smaller default postgresql.conf}}<br />
}}<br />
<br />
{{TodoItem<br />
|Document support for N<nowiki>' '</nowiki> national character string literals, if it matches the SQL standard<br />
* http://archives.postgresql.org/message-id/1275895438.1849.1.camel@fsopti579.F-Secure.com<br />
}}<br />
<br />
== Exotic Features ==<br />
<br />
{{TodoItem<br />
|Add pre-parsing phase that converts non-ISO syntax to supported syntax<br />
|This could allow SQL written for other databases to run without modification.}}<br />
<br />
{{TodoItem<br />
|Allow plug-in modules to emulate features from other databases}}<br />
<br />
{{TodoItem<br />
|Add features of Oracle-style packages<br />
|A package would be a schema with session-local variables, public/private functions, and initialization functions. It is also possible to implement these capabilities in any schema and not use a separate &quot;packages&quot; syntax at all.<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php <nowiki>proposal for PL packages for 8.3.</nowiki>]<br />
* [http://www.postgresql.org/message-id/CAFj8pRD4OAXp2zp7dBRg5eo6X3rtT5MHTMVRN1e1kdK8xE6E4g@mail.gmail.com proposal: schema PL session variables]<br />
* [https://www.postgresql.org/message-id/CAFj8pRCfdTLeJbTSbAFOwhuS-aWaJ61w59XwKLcVYQFAVwfVCw%40mail.gmail.com proposal: session server side variables]<br />
* [https://www.postgresql.org/message-id/81060c9d-73df-2266-8857-d584164bb699%40commandprompt.com Packages: Again]<br />
}}<br />
<br />
{{TodoItem<br />
|Consider allowing control of upper/lower case folding of unquoted identifiers<br />
* [http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php <nowiki>Bringing PostgreSQL torwards the standard regarding case folding</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php <nowiki>Re: [SQL] Case Preservation disregarding case sensitivity?</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php <nowiki>TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php <nowiki>Identifier case folding notes</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php <nowiki>Identifier case folding notes</nowiki>]<br />
* [https://www.postgresql.org/message-id/ACF85C502E55A143AB9F4ECFE960660A17282D@mailserver2.local.mstarlabs.com Cluster wide option to control symbol case folding]<br />
}}<br />
<br />
{{TodoItem<br />
|Add autonomous transactions<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php <nowiki>autonomous transactions</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Give query progress indication<br />
* [[Query progress indication]]<br />
}}<br />
<br />
{{TodoItem<br />
|Rethink our type system<br />
* [[Rethinking datatypes]]<br />
}}<br />
<br />
== Features We Do ''Not'' Want ==<br />
<br />
The following features have been discussed ad nauseum on the PostgreSQL mailing lists and the consensus has been that the project is not interested in them. As such, if you are going to bring them up as potential features, you will want to be familiar with all of the arguments against these features which have been previously made over the years. If you decide to work on such features anyway, you should be aware that you face a higher-than-normal barrier to get the Project to accept them.<br />
<br />
{{TodoItem<br />
|Rewrite the code in a different language (not wanted)<br />
* https://www.postgresql.org/message-id/CAASwCXdQUiuUnhycdRvrUmHuzk5PsaGxr54U4t34teQjcjb%3DAQ%40mail.gmail.com<br />
* https://www.postgresql.org/message-id/CANvSX4wsVhDrqy4Ku81wHs%2D%2DaViYthJ_G5G-2VeZ%3DJboEE9TNQ%40mail.gmail.com<br />
}}<br />
<br />
{{TodoItem<br />
|All backends running as threads in a single process (not wanted)<br />
|This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve. Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features. Moving to a threaded engine would also require halting all other work on PostgreSQL for one to two years.<br />
* [https://www.postgresql.org/message-id/942824238.20160712165757@bitec.ru One process per session lack of sharing]<br />
}}<br />
<br />
{{TodoItem<br />
|"Oracle-style" optimizer hints (not wanted)<br />
|Optimizer hints, as implemented in Oracle and other RDBMSes, are used to work around problems in the optimizer and introduce upgrade and maintenance issues. We would rather have such problems reported and fixed. We have discussed a more sophisticated system of per-class cost adjustment instead, but a specification remains to be developed. See [[OptimizerHintsDiscussion|Optimizer Hints Discussion]] for further information.}}<br />
<br />
{{TodoItem<br />
|Embedded server (not wanted)<br />
|While PostgreSQL clients runs fine in limited-resource environments, the server requires multiple processes and a stable pool of resources to run reliably and efficiently. Stripping down the PostgreSQL server to run in the same process address space as the client application would add too much complexity and failure cases. Besides, there are several very mature embedded SQL databases already available.}}<br />
<br />
{{TodoItem<br />
|Obfuscated function source code (not wanted)<br />
|Obfuscating function source code has minimal protective benefits because anyone with super-user access can find a way to view the code. At the same time, it would greatly complicate backups and other administrative tasks. To prevent non-super-users from viewing function source code, remove SELECT permission on pg_proc.<br />
* [http://archives.postgresql.org/pgsql-general/2008-09/msg00668.php <nowiki>Obfuscated stored procedures (was Re: Oracle and Postgresql)</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|Indeterminate behavior for the GROUP BY clause (not wanted)<br />
|At least one other database product allows specification of a subset of the result columns which GROUP BY would need to be able to provide predictable results; the server is free to return any value from the group. This is not viewed as a desirable feature. PostgreSQL 9.1 allows result columns that are not referenced by GROUP BY if a primary key for the same table is referenced in GROUP BY.<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-03/msg00297.php <nowiki>Re: SQL compatibility reminder: MySQL vs PostgreSQL</nowiki>]<br />
}}<br />
<br />
{{TodoItem<br />
|On-disk bitmap indexes (not wanted)<br />
|The rigidity of on-disk bitmap indexes, and the existence of GIN and in-memory bitmaps make this undesirable.<br />
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php <nowiki>Re: Bitmap index AM</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php <nowiki>Bitmap index thoughts</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php <nowiki>Stream bitmaps</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php <nowiki>Re: Bitmapscan changes - Requesting further feedback</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php <nowiki>Updated bitmap index patch</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php <nowiki>Reviewing new index types (was Re: [PATCHES] Updated bitmap indexpatch)</nowiki>]<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01023.php <nowiki>Bitmap Indexes: request for feedback</nowiki>]<br />
* [http://archives.postgresql.org/message-id/800923.27831.qm@web29010.mail.ird.yahoo.com <nowiki>bitmap indexes - performance</nowiki>]<br />
* [http://www.postgresql.org/message-id/20130914181424.GA24448@toroid.org <nowiki>[PATCH] bitmap indexes</nowiki>]<br />
}}<br />
<br />
[[Category:Todo]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37247PostgreSQL 15 Open Items2022-09-28T23:31:24Z<p>Davidrowley: /* resolved before 15rc2 */ Fix broken syntax</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
* [https://www.postgresql.org/message-id/flat/YxfagaTXUNa9ggLb@ahch-to pgstat: START_REPLICATION SLOT assertion failure]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
* [https://www.postgresql.org/message-id/17485-396609c6925b982d%40postgresql.org Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|e28bb885196916b0a3d898ae4f2be0e38108d81b}}<br />
<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|7201cd1862}}<br />
<br />
* [https://www.postgresql.org/message-id/f8a4105f076544c180a87ef0c4822352%40stmuk.bayern.de Extension pg_trgm, permissions and pg_dump order]<br />
** Affects all stable branches.<br />
** Fixed by {{PgCommitURL|00377b9a02b89a831ae50e1c718d34565356698f}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15rc2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CACawEhVxe0ufR26UcqtU7GYGRuubq3p6ZWPGXL4cxy_uexpAAQ%40mail.gmail.com Memory leak in single-column sorts]<br />
** Fixed by: {{PgCommitURL|f7ae8a2e186ca27f4ea64fddc21bfabaf0618507}}<br />
<br />
=== resolved before 15rc1 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220831140128.GS31833%40telsasoft.com recovery fails with recovery_prefetch=on and maintenance_io_concurency=0]<br />
** Fixed by: {{PgCommitURL|adb466150b44d1eaf43a2d22f58ff4c545a0ed3f}}<br />
* [https://www.postgresql.org/message-id/20220912014235.GC31833@telsasoft.com FailedAssertion("TransactionIdIsValid(xmax)]<br />
** Fixed by: {{PgCommitURL|adb466150b44d1eaf43a2d22f58ff4c545a0ed3f}}<br />
* [https://www.postgresql.org/message-id/Yxa1SU4nH2HfN3/i%40ahch-to pg_publication_tables view is busted]<br />
** Fixed by: {{PgCommitURL|20b6847176976da9cae6103475b967e6c2971898}}<br />
* [https://www.postgresql.org/message-id/flat/20220902115511.GY31833%40telsasoft.com#ebfa4e87b4247318ccd1e233c7c9af4a replaying wal_compression=lz4/zstd on a server which doesn't support it exposes an elog() which includes no information about the failure]<br />
** Owner: Michael Paquier (4035cd5)<br />
** Fixed by: {{PgCommitURL|df4a056619a7e9868ec43a15e2088ff8ccf94471}}<br />
* [https://www.postgresql.org/message-id/flat/20220819133016.GV26426@telsasoft.com syntax error in MERGE docs]<br />
** Fixed by: {{PgCommitURL|5dcebd10baa8ec14a97029ca0bacaf2a9a0f8652}}<br />
* [https://www.postgresql.org/message-id/181A6DA8-3B7F-4B71-82D5-363FF0146820@yesql.se pg_upgrade generated files in subdir follow-up]<br />
** Fixed by: {{PgCommitURL|ee5353abb6124de5ffd24ef1cedbc2a7196d4fd5}}<br />
* [https://www.postgresql.org/message-id/1400032.1662217889@sss.pgh.pa.us pg_basebackup's --gzip switch misbehaves]<br />
** Fixed by: {{PgCommitURL|f352e2d08ac048d7407dd6098fc6b344ff85c2dd}}<br />
* [https://www.postgresql.org/message-id/CAFiTN-sE3ry=ycMPVtC+Djw4Fd7gbUGVv_qqw6qfzp=JLvqT3g@mail.gmail.com Assertion failure in WaitForWALToBecomeAvailable state machine]<br />
** Fixed by: {{PgCommitURL|b4f584f9d2a1b50d1f5ce88408a54bb11f1c8353}}<br />
* [https://www.postgresql.org/message-id/6dd6db0984d86a51b7255ba79f111971@postgrespro.ru Possible to create database with incompatible ICU and encoding settings]<br />
** Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|c7db01e325a530ec38ec7ba57cd3ed32e123e33c}}<br />
* [https://www.postgresql.org/message-id/flat/20220912005443.GB31833%40telsasoft.com#b900d448bc57e46da3a235219034ba4c startup process says "recovering NNN" after it's done recovering NNN]<br />
** Fixed by: {{PgCommitURL|fbb5f54b67c2f35c885d07daa26bce7e2eb6b0be}}<br />
* [https://www.postgresql.org/message-id/2729c9e2-9aac-8cda-f2f4-34f2bcc18f4e%40enterprisedb.com why can't a table be part of the same publication as its schema]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|13a185f54ba594a5fb42bac3e1ecbdfd62b9041f}}<br />
<br />
=== resolved before 15beta4 ===<br />
<br />
* [https://www.postgresql.org/message-id/17579-82482cd7b267b862%40postgresql.org MERGE fails if inside a CTE]<br />
** Fixed by: {{PgCommitURL|455d254d22665eb}}<br />
* [https://www.postgresql.org/message-id/CACawEhXwHN3X34FiwoYG8vXR-oyUdrp7qcfRWSzS+NPahS5gSw@mail.gmail.com Materialized view rewrite is broken when there is an event trigger]<br />
** Owner: Michael Paquier (b0483263dda0824cc49e3f8a022dab07e1cdf9a7)<br />
** Fixed by: {{PgCommitURL|93f2349c36a7555a81d5e26edf9a0213fb3d323a}}<br />
* [https://www.postgresql.org/message-id/20220802175043.GA13682@telsasoft.com CREATE DATABASE STRATEGY WAL_LOG crash and memory corruption]<br />
** Owner: Robert Haas (9c08aea6a3090a396be334cc58c511edab05776a)<br />
* [https://www.postgresql.org/message-id/20220818133406.GL26426@telsasoft.com crash in parallel vacuum]<br />
** Fixed by: {{PgCommitURL|662ba729a67e5c6e43efbc5263e1d2c3a72a8741}}<br />
* [https://www.postgresql.org/message-id/flat/f385ba25e7f8be427b8c582e5cca7d79%40postgrespro.ru Crash in ICU for global collation]<br />
** Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** One issue has been fixed in 36f729e2bc3539e777cda698dc441b8ccec42142 but we still have a problem with [https://www.postgresql.org/message-id/7ad26354e75259f59c4a6c6997b8ee32@postgrespro.ru pg_collation.colliculocale not getting dumped]<br />
** Fixed by: {{PgCommitURL|396d348b046c6b7e5dc83158c4c1df1377a1d2ef}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGLptJc_k=cEqGtyRb-2pyF++uUMNi-+VEhrUV6pmezJmg@mail.gmail.com PANIC during standby promotion]<br />
** Fixed by: {{PgCommitURL|932b01630095a08797e05ba1dae279731b862c95}}<br />
* [https://www.postgresql.org/message-id/aada8f97-924e-5661-aead-257aa346899c@enterprisedb.com GROUP BY optimization defeated partitionwise tests]<br />
** [https://www.postgresql.org/message-id/3242058.1659563057%40sss.pgh.pa.us Possibly-related complaint here]<br />
** Owner: Tomas Vondra (db0d67db2)<br />
** Fixed by: {{PgCommitURL|2fe6b2a806f20f2dbf02c6e79783dbc2777a1840}}<br />
<br />
=== resolved before 15beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvrHQkiFRHiGiAS-LMOvJN-eK-s762=tVzBz8ZqUea-a_A@mail.gmail.com tuplesort Generation memory contexts don't play nicely with index builds]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|ae1123f9899fe80935ae344e38f18632beb1bf9a}}<br />
* [https://www.postgresql.org/message-id/YrpVkADAY0knF6vM@paquier.xyz Repeatability of installcheck for test_oat_hooks]<br />
** Owner: Andrew Dunstan<br />
** Fixed by: {{PgCommitURL|a6434b951558baad8372dc4b83bf87606dac9cda}}<br />
* [https://www.postgresql.org/message-id/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de Revert debugging added due to 019_replslot_limit]<br />
** Owner: Andres Freund<br />
** Reverted: {{PgCommitURL|3f8148c256e067dc2e8929ed174671ba7dc3339c}}<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220706224727.GA2158260@nathanxps13 pg_parameter_aclcheck() and trusted extensions]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
** Fixed by: {{PgCommitURL|13d83881514856353dc86575eb0fc28132349a60}}<br />
* [https://www.postgresql.org/message-id/YtjsbtZFCaou6C/k@paquier.xyz Unprivileged user can induce crash by using an SUSET param in PGOPTIONS]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
** Fixed by: {{PgCommitURL|b35617de37870756bdb0e00ffc0a42441e56eefa}}<br />
* [https://www.postgresql.org/message-id/20220726050402.vsr6fmz7rsgpmdz3@jrouhaud wrong filename used in pg_ident_file_mapping infrastructure]<br />
** Owner: Michael Paquier (a2c84990bea7beadb599d02328190e2a763dcb86)<br />
** Fixed by: {{PgCommitURL|27e0ee57f68d27af68967759a2ff61a581f501dc}}<br />
* [https://www.postgresql.org/message-id/17558-3f6599ffcf52fd4a%40postgresql.org Endless loop with UNIQUE NULLS NOT DISTINCT and INSERT ... ON CONFLICT]<br />
** Owner: Peter Eisentraut (94aa7cc5f707712f592885995a28e018c7c80488)<br />
** Fixed by: {{PgCommitURL|d59383924c580a77a2346d9b1284c8589b3d43e2}}<br />
* [https://www.postgresql.org/message-id/PA4P191MB160009A09B9D0624359278CFBA9F9@PA4P191MB1600.EURP191.PROD.OUTLOOK.COM XX000 error caused by window function run conditions]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|270eb4b5d4986534f2d522ebb19f67396d13cf44}}<br />
<br />
* [https://www.postgresql.org/message-id/20220701231413.GI13040@telsasoft.com large objects lost on upgrade]<br />
** Owner: Robert Haas (9a974cbcba005256a19991203583a94b4f9a21a9)<br />
** Fixed by: {{PgCommitURL|bbe08b8869bd29d587f24ef18eb45c7d4d14afca}}<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
** Fixed by: {{PgCommitURL|b4529005fd387e863bfa9eb863629b1183c0449c}}<br />
* [https://www.postgresql.org/message-id/f80ace33-11fb-1cd3-20f8-98f51d151088@enterprisedb.com pg_upgrade test writes to source directory]<br />
** Owner: Michael Paquier (322becb6085cb92d3708635eea61b45776bf27b6)<br />
** Fixed by: {{PgCommitURL|15b6d2155375dee2fcba072fffa03c1c8b44656c}}<br />
* [https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com pg_upgrade is not idempotent, even with --check]<br />
** Owner: Michael Paquier (38bfae36526636ef55daf7cf2a3282403587cb5b)<br />
** Fixed by: {{PgCommitURL|4fff78f00910af0137f9de7532f8eb21d08ab1c3}}<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|fd0b9dcebda7b931a41ce5c8e86d13f2efd0af2e}}<br />
* [https://www.postgresql.org/message-id/05ebcb44-f383-86e3-4f31-0a97a55634cf%40enterprisedb.com Ignoring BRIN for HOT udpates seems broken]<br />
** Owner: Tomas Vondra (5753d4ee320b)<br />
** Fixed by: {{PgCommitURL|e3fcca0d0d2414f3a50d6fd40eddf48b7df81475}}<br />
* [https://www.postgresql.org/message-id/PAXPR02MB760039506C87A2083AD85575E3DA9%40PAXPR02MB7600.eurprd02.prod.outlook.com psql no longer reports NOTICE messages promptly]<br />
** Owner: Peter Eisentraut (7844c9918)<br />
** Fixed by: {{PgCommitURL|e77de23fbb0f4ef27090c144edcfa889bb2a06d5}}<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
** Fixed by: {{PgCommitURL|e243de03fb4583dd4a9f0afb41493727d7946c02}}<br />
* [https://www.postgresql.org/message-id/20220607154744.vvmitnqhyxrne5ms%40jrouhaud COPY WITH (HEADER MATCH) broken with custom attribute list]<br />
** Owner: Peter Eisentraut (072132f04e55c1c3b0f1a582318da78de7334379)<br />
** Fixed by: {{PgCommitURL|ca7a0d1d368216e89359c63531a4df0b99a437e4}}<br />
* [https://www.postgresql.org/message-id/flat/DM4PR84MB17349C4E7D88A68264C18AF3EED69%40DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual]<br />
** Tomas Vondra<br />
** Fixed by: {{PgCommitURL|401f623c7b14890011b9bb9dda7639b1de4d40ad}}<br />
* [https://www.postgresql.org/message-id/20220625151930.GH22452@telsasoft.com Incorrect version check for datlocprovider in pg_upgrade]<br />
** Owner: Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|fa06a34d14ea053e1e405a6ab2a1c3f1631c3a5e}}<br />
* [https://www.postgresql.org/message-id/17522-bfcd5c603b5f4daa@postgresql.org Failure in TAP tests for IP address support in SANs with LibreSSL]<br />
** Owner: Peter Eisentraut (c1932e542863f0f646f005b3492452acc57c7e66)<br />
** Fixed by: {{PgCommitURL|901a9d53011573e45cd7b87682f0520ef3b0fd2d}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
<br />
<br />
== Won't Fix ==<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Problem showed by 90efa2f5565d28054c30c18f6a2f17f94fdff91e.<br />
* [https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de Reduce amount of logs generated by TAP tests of pg_upgrade?]<br />
** Owner: Michael Paquier<br />
** Other thread: [https://www.postgresql.org/message-id/YrP6ZRXITYWhpVrl@paquier.xyz here]<br />
** The problem is wider than just the upgrade tests, as all the runs of pg_regress would be impacted. We may want a more centralized solution for this older problem.<br />
* [https://www.postgresql.org/message-id/CABOikdM+cR6fDd1XkGu0paKWaa1E_s4WRG3oETw8u_U5NK1oeg@mail.gmail.com Assertion failure on PG15 with modified test_shm_mq test]<br />
** Owner: Andres Freund<br />
** on the thread, andres says that doesn't seem realistic to fix this, extensions will need to work around it<br />
* [https://www.postgresql.org/message-id/20220616233130.rparivafipt6doj3%40alap3.anarazel.de PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size]<br />
** Owner: Andrew Dunstan<br />
** Feature reverted. Fixes will be made in a future release.<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: June 30, 2022<br />
* Beta 3: August 11, 2022<br />
* Beta 4: September 8, 2022<br />
* RC 1: September 29, 2022<br />
* GA: October 13, 2022<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37246PostgreSQL 15 Open Items2022-09-28T23:30:10Z<p>Davidrowley: Mark "Memory leak in single-column sorts" as fixed before rc2</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
* [https://www.postgresql.org/message-id/flat/YxfagaTXUNa9ggLb@ahch-to pgstat: START_REPLICATION SLOT assertion failure]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
* [https://www.postgresql.org/message-id/17485-396609c6925b982d%40postgresql.org Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|e28bb885196916b0a3d898ae4f2be0e38108d81b}}<br />
<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|7201cd1862}}<br />
<br />
* [https://www.postgresql.org/message-id/f8a4105f076544c180a87ef0c4822352%40stmuk.bayern.de Extension pg_trgm, permissions and pg_dump order]<br />
** Affects all stable branches.<br />
** Fixed by {{PgCommitURL|00377b9a02b89a831ae50e1c718d34565356698f}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15rc2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CACawEhVxe0ufR26UcqtU7GYGRuubq3p6ZWPGXL4cxy_uexpAAQ%40mail.gmail.com Memory leak in single-column sorts]<br />
** Fixed by: [[PgCommitURL|f7ae8a2e186ca27f4ea64fddc21bfabaf0618507}<br />
<br />
=== resolved before 15rc1 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220831140128.GS31833%40telsasoft.com recovery fails with recovery_prefetch=on and maintenance_io_concurency=0]<br />
** Fixed by: {{PgCommitURL|adb466150b44d1eaf43a2d22f58ff4c545a0ed3f}}<br />
* [https://www.postgresql.org/message-id/20220912014235.GC31833@telsasoft.com FailedAssertion("TransactionIdIsValid(xmax)]<br />
** Fixed by: {{PgCommitURL|adb466150b44d1eaf43a2d22f58ff4c545a0ed3f}}<br />
* [https://www.postgresql.org/message-id/Yxa1SU4nH2HfN3/i%40ahch-to pg_publication_tables view is busted]<br />
** Fixed by: {{PgCommitURL|20b6847176976da9cae6103475b967e6c2971898}}<br />
* [https://www.postgresql.org/message-id/flat/20220902115511.GY31833%40telsasoft.com#ebfa4e87b4247318ccd1e233c7c9af4a replaying wal_compression=lz4/zstd on a server which doesn't support it exposes an elog() which includes no information about the failure]<br />
** Owner: Michael Paquier (4035cd5)<br />
** Fixed by: {{PgCommitURL|df4a056619a7e9868ec43a15e2088ff8ccf94471}}<br />
* [https://www.postgresql.org/message-id/flat/20220819133016.GV26426@telsasoft.com syntax error in MERGE docs]<br />
** Fixed by: {{PgCommitURL|5dcebd10baa8ec14a97029ca0bacaf2a9a0f8652}}<br />
* [https://www.postgresql.org/message-id/181A6DA8-3B7F-4B71-82D5-363FF0146820@yesql.se pg_upgrade generated files in subdir follow-up]<br />
** Fixed by: {{PgCommitURL|ee5353abb6124de5ffd24ef1cedbc2a7196d4fd5}}<br />
* [https://www.postgresql.org/message-id/1400032.1662217889@sss.pgh.pa.us pg_basebackup's --gzip switch misbehaves]<br />
** Fixed by: {{PgCommitURL|f352e2d08ac048d7407dd6098fc6b344ff85c2dd}}<br />
* [https://www.postgresql.org/message-id/CAFiTN-sE3ry=ycMPVtC+Djw4Fd7gbUGVv_qqw6qfzp=JLvqT3g@mail.gmail.com Assertion failure in WaitForWALToBecomeAvailable state machine]<br />
** Fixed by: {{PgCommitURL|b4f584f9d2a1b50d1f5ce88408a54bb11f1c8353}}<br />
* [https://www.postgresql.org/message-id/6dd6db0984d86a51b7255ba79f111971@postgrespro.ru Possible to create database with incompatible ICU and encoding settings]<br />
** Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|c7db01e325a530ec38ec7ba57cd3ed32e123e33c}}<br />
* [https://www.postgresql.org/message-id/flat/20220912005443.GB31833%40telsasoft.com#b900d448bc57e46da3a235219034ba4c startup process says "recovering NNN" after it's done recovering NNN]<br />
** Fixed by: {{PgCommitURL|fbb5f54b67c2f35c885d07daa26bce7e2eb6b0be}}<br />
* [https://www.postgresql.org/message-id/2729c9e2-9aac-8cda-f2f4-34f2bcc18f4e%40enterprisedb.com why can't a table be part of the same publication as its schema]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|13a185f54ba594a5fb42bac3e1ecbdfd62b9041f}}<br />
<br />
=== resolved before 15beta4 ===<br />
<br />
* [https://www.postgresql.org/message-id/17579-82482cd7b267b862%40postgresql.org MERGE fails if inside a CTE]<br />
** Fixed by: {{PgCommitURL|455d254d22665eb}}<br />
* [https://www.postgresql.org/message-id/CACawEhXwHN3X34FiwoYG8vXR-oyUdrp7qcfRWSzS+NPahS5gSw@mail.gmail.com Materialized view rewrite is broken when there is an event trigger]<br />
** Owner: Michael Paquier (b0483263dda0824cc49e3f8a022dab07e1cdf9a7)<br />
** Fixed by: {{PgCommitURL|93f2349c36a7555a81d5e26edf9a0213fb3d323a}}<br />
* [https://www.postgresql.org/message-id/20220802175043.GA13682@telsasoft.com CREATE DATABASE STRATEGY WAL_LOG crash and memory corruption]<br />
** Owner: Robert Haas (9c08aea6a3090a396be334cc58c511edab05776a)<br />
* [https://www.postgresql.org/message-id/20220818133406.GL26426@telsasoft.com crash in parallel vacuum]<br />
** Fixed by: {{PgCommitURL|662ba729a67e5c6e43efbc5263e1d2c3a72a8741}}<br />
* [https://www.postgresql.org/message-id/flat/f385ba25e7f8be427b8c582e5cca7d79%40postgrespro.ru Crash in ICU for global collation]<br />
** Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** One issue has been fixed in 36f729e2bc3539e777cda698dc441b8ccec42142 but we still have a problem with [https://www.postgresql.org/message-id/7ad26354e75259f59c4a6c6997b8ee32@postgrespro.ru pg_collation.colliculocale not getting dumped]<br />
** Fixed by: {{PgCommitURL|396d348b046c6b7e5dc83158c4c1df1377a1d2ef}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGLptJc_k=cEqGtyRb-2pyF++uUMNi-+VEhrUV6pmezJmg@mail.gmail.com PANIC during standby promotion]<br />
** Fixed by: {{PgCommitURL|932b01630095a08797e05ba1dae279731b862c95}}<br />
* [https://www.postgresql.org/message-id/aada8f97-924e-5661-aead-257aa346899c@enterprisedb.com GROUP BY optimization defeated partitionwise tests]<br />
** [https://www.postgresql.org/message-id/3242058.1659563057%40sss.pgh.pa.us Possibly-related complaint here]<br />
** Owner: Tomas Vondra (db0d67db2)<br />
** Fixed by: {{PgCommitURL|2fe6b2a806f20f2dbf02c6e79783dbc2777a1840}}<br />
<br />
=== resolved before 15beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvrHQkiFRHiGiAS-LMOvJN-eK-s762=tVzBz8ZqUea-a_A@mail.gmail.com tuplesort Generation memory contexts don't play nicely with index builds]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|ae1123f9899fe80935ae344e38f18632beb1bf9a}}<br />
* [https://www.postgresql.org/message-id/YrpVkADAY0knF6vM@paquier.xyz Repeatability of installcheck for test_oat_hooks]<br />
** Owner: Andrew Dunstan<br />
** Fixed by: {{PgCommitURL|a6434b951558baad8372dc4b83bf87606dac9cda}}<br />
* [https://www.postgresql.org/message-id/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de Revert debugging added due to 019_replslot_limit]<br />
** Owner: Andres Freund<br />
** Reverted: {{PgCommitURL|3f8148c256e067dc2e8929ed174671ba7dc3339c}}<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220706224727.GA2158260@nathanxps13 pg_parameter_aclcheck() and trusted extensions]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
** Fixed by: {{PgCommitURL|13d83881514856353dc86575eb0fc28132349a60}}<br />
* [https://www.postgresql.org/message-id/YtjsbtZFCaou6C/k@paquier.xyz Unprivileged user can induce crash by using an SUSET param in PGOPTIONS]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
** Fixed by: {{PgCommitURL|b35617de37870756bdb0e00ffc0a42441e56eefa}}<br />
* [https://www.postgresql.org/message-id/20220726050402.vsr6fmz7rsgpmdz3@jrouhaud wrong filename used in pg_ident_file_mapping infrastructure]<br />
** Owner: Michael Paquier (a2c84990bea7beadb599d02328190e2a763dcb86)<br />
** Fixed by: {{PgCommitURL|27e0ee57f68d27af68967759a2ff61a581f501dc}}<br />
* [https://www.postgresql.org/message-id/17558-3f6599ffcf52fd4a%40postgresql.org Endless loop with UNIQUE NULLS NOT DISTINCT and INSERT ... ON CONFLICT]<br />
** Owner: Peter Eisentraut (94aa7cc5f707712f592885995a28e018c7c80488)<br />
** Fixed by: {{PgCommitURL|d59383924c580a77a2346d9b1284c8589b3d43e2}}<br />
* [https://www.postgresql.org/message-id/PA4P191MB160009A09B9D0624359278CFBA9F9@PA4P191MB1600.EURP191.PROD.OUTLOOK.COM XX000 error caused by window function run conditions]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|270eb4b5d4986534f2d522ebb19f67396d13cf44}}<br />
<br />
* [https://www.postgresql.org/message-id/20220701231413.GI13040@telsasoft.com large objects lost on upgrade]<br />
** Owner: Robert Haas (9a974cbcba005256a19991203583a94b4f9a21a9)<br />
** Fixed by: {{PgCommitURL|bbe08b8869bd29d587f24ef18eb45c7d4d14afca}}<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
** Fixed by: {{PgCommitURL|b4529005fd387e863bfa9eb863629b1183c0449c}}<br />
* [https://www.postgresql.org/message-id/f80ace33-11fb-1cd3-20f8-98f51d151088@enterprisedb.com pg_upgrade test writes to source directory]<br />
** Owner: Michael Paquier (322becb6085cb92d3708635eea61b45776bf27b6)<br />
** Fixed by: {{PgCommitURL|15b6d2155375dee2fcba072fffa03c1c8b44656c}}<br />
* [https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com pg_upgrade is not idempotent, even with --check]<br />
** Owner: Michael Paquier (38bfae36526636ef55daf7cf2a3282403587cb5b)<br />
** Fixed by: {{PgCommitURL|4fff78f00910af0137f9de7532f8eb21d08ab1c3}}<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|fd0b9dcebda7b931a41ce5c8e86d13f2efd0af2e}}<br />
* [https://www.postgresql.org/message-id/05ebcb44-f383-86e3-4f31-0a97a55634cf%40enterprisedb.com Ignoring BRIN for HOT udpates seems broken]<br />
** Owner: Tomas Vondra (5753d4ee320b)<br />
** Fixed by: {{PgCommitURL|e3fcca0d0d2414f3a50d6fd40eddf48b7df81475}}<br />
* [https://www.postgresql.org/message-id/PAXPR02MB760039506C87A2083AD85575E3DA9%40PAXPR02MB7600.eurprd02.prod.outlook.com psql no longer reports NOTICE messages promptly]<br />
** Owner: Peter Eisentraut (7844c9918)<br />
** Fixed by: {{PgCommitURL|e77de23fbb0f4ef27090c144edcfa889bb2a06d5}}<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
** Fixed by: {{PgCommitURL|e243de03fb4583dd4a9f0afb41493727d7946c02}}<br />
* [https://www.postgresql.org/message-id/20220607154744.vvmitnqhyxrne5ms%40jrouhaud COPY WITH (HEADER MATCH) broken with custom attribute list]<br />
** Owner: Peter Eisentraut (072132f04e55c1c3b0f1a582318da78de7334379)<br />
** Fixed by: {{PgCommitURL|ca7a0d1d368216e89359c63531a4df0b99a437e4}}<br />
* [https://www.postgresql.org/message-id/flat/DM4PR84MB17349C4E7D88A68264C18AF3EED69%40DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual]<br />
** Tomas Vondra<br />
** Fixed by: {{PgCommitURL|401f623c7b14890011b9bb9dda7639b1de4d40ad}}<br />
* [https://www.postgresql.org/message-id/20220625151930.GH22452@telsasoft.com Incorrect version check for datlocprovider in pg_upgrade]<br />
** Owner: Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|fa06a34d14ea053e1e405a6ab2a1c3f1631c3a5e}}<br />
* [https://www.postgresql.org/message-id/17522-bfcd5c603b5f4daa@postgresql.org Failure in TAP tests for IP address support in SANs with LibreSSL]<br />
** Owner: Peter Eisentraut (c1932e542863f0f646f005b3492452acc57c7e66)<br />
** Fixed by: {{PgCommitURL|901a9d53011573e45cd7b87682f0520ef3b0fd2d}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
<br />
<br />
== Won't Fix ==<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Problem showed by 90efa2f5565d28054c30c18f6a2f17f94fdff91e.<br />
* [https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de Reduce amount of logs generated by TAP tests of pg_upgrade?]<br />
** Owner: Michael Paquier<br />
** Other thread: [https://www.postgresql.org/message-id/YrP6ZRXITYWhpVrl@paquier.xyz here]<br />
** The problem is wider than just the upgrade tests, as all the runs of pg_regress would be impacted. We may want a more centralized solution for this older problem.<br />
* [https://www.postgresql.org/message-id/CABOikdM+cR6fDd1XkGu0paKWaa1E_s4WRG3oETw8u_U5NK1oeg@mail.gmail.com Assertion failure on PG15 with modified test_shm_mq test]<br />
** Owner: Andres Freund<br />
** on the thread, andres says that doesn't seem realistic to fix this, extensions will need to work around it<br />
* [https://www.postgresql.org/message-id/20220616233130.rparivafipt6doj3%40alap3.anarazel.de PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size]<br />
** Owner: Andrew Dunstan<br />
** Feature reverted. Fixes will be made in a future release.<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: June 30, 2022<br />
* Beta 3: August 11, 2022<br />
* Beta 4: September 8, 2022<br />
* RC 1: September 29, 2022<br />
* GA: October 13, 2022<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37141PostgreSQL 15 Open Items2022-08-04T22:18:35Z<p>Davidrowley: Mark "XX000 error caused by window function run conditions" as fixed</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20220616233130.rparivafipt6doj3%40alap3.anarazel.de PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size]<br />
** Owner: Andrew Dunstan<br />
* [https://www.postgresql.org/message-id/aada8f97-924e-5661-aead-257aa346899c@enterprisedb.com GROUP BY optimization defeated partitionwise tests]<br />
** [https://www.postgresql.org/message-id/3242058.1659563057%40sss.pgh.pa.us Possibly-related complaint here]<br />
** Owner: Tomas Vondra (db0d67db2)<br />
* [https://www.postgresql.org/message-id/20220802175043.GA13682@telsasoft.com CREATE DATABASE STRATEGY WAL_LOG crash and memory corruption]<br />
** Owner: Robert Haas (9c08aea6a3090a396be334cc58c511edab05776a)<br />
* [https://www.postgresql.org/message-id/20220701231413.GI13040@telsasoft.com large objects lost on upgrade]<br />
** Owner: Robert Haas (9a974cbcba005256a19991203583a94b4f9a21a9)<br />
** Fixed by: {{PgCommitURL|bbe08b8869bd29d587f24ef18eb45c7d4d14afca}}<br />
** [https://www.postgresql.org/message-id/2657259.1659460333%40sss.pgh.pa.us Test failure reported]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
* [https://www.postgresql.org/message-id/17485-396609c6925b982d%40postgresql.org Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|e28bb885196916b0a3d898ae4f2be0e38108d81b}}<br />
<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|7201cd1862}}<br />
<br />
* [https://www.postgresql.org/message-id/f8a4105f076544c180a87ef0c4822352%40stmuk.bayern.de Extension pg_trgm, permissions and pg_dump order]<br />
** Affects all stable branches.<br />
** Fixed by {{PgCommitURL|00377b9a02b89a831ae50e1c718d34565356698f}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvrHQkiFRHiGiAS-LMOvJN-eK-s762=tVzBz8ZqUea-a_A@mail.gmail.com tuplesort Generation memory contexts don't play nicely with index builds]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|ae1123f9899fe80935ae344e38f18632beb1bf9a}}<br />
* [https://www.postgresql.org/message-id/YrpVkADAY0knF6vM@paquier.xyz Repeatability of installcheck for test_oat_hooks]<br />
** Owner: Andrew Dunstan<br />
** Fixed by: {{PgCommitURL|a6434b951558baad8372dc4b83bf87606dac9cda}}<br />
* [https://www.postgresql.org/message-id/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de Revert debugging added due to 019_replslot_limit]<br />
** Owner: Andres Freund<br />
** Reverted: {{PgCommitURL|3f8148c256e067dc2e8929ed174671ba7dc3339c}}<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220706224727.GA2158260@nathanxps13 pg_parameter_aclcheck() and trusted extensions]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
** Fixed by: {{PgCommitURL|13d83881514856353dc86575eb0fc28132349a60}}<br />
* [https://www.postgresql.org/message-id/YtjsbtZFCaou6C/k@paquier.xyz Unprivileged user can induce crash by using an SUSET param in PGOPTIONS]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
** Fixed by: {{PgCommitURL|b35617de37870756bdb0e00ffc0a42441e56eefa}}<br />
* [https://www.postgresql.org/message-id/20220726050402.vsr6fmz7rsgpmdz3@jrouhaud wrong filename used in pg_ident_file_mapping infrastructure]<br />
** Owner: Michael Paquier (a2c84990bea7beadb599d02328190e2a763dcb86)<br />
** Fixed by: {{PgCommitURL|27e0ee57f68d27af68967759a2ff61a581f501dc}}<br />
* [https://www.postgresql.org/message-id/17558-3f6599ffcf52fd4a%40postgresql.org Endless loop with UNIQUE NULLS NOT DISTINCT and INSERT ... ON CONFLICT]<br />
** Owner: Peter Eisentraut (94aa7cc5f707712f592885995a28e018c7c80488)<br />
** Fixed by: {{PgCommitURL|d59383924c580a77a2346d9b1284c8589b3d43e2}}<br />
* [https://www.postgresql.org/message-id/PA4P191MB160009A09B9D0624359278CFBA9F9@PA4P191MB1600.EURP191.PROD.OUTLOOK.COM XX000 error caused by window function run conditions]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|270eb4b5d4986534f2d522ebb19f67396d13cf44}}<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
** Fixed by: {{PgCommitURL|b4529005fd387e863bfa9eb863629b1183c0449c}}<br />
* [https://www.postgresql.org/message-id/f80ace33-11fb-1cd3-20f8-98f51d151088@enterprisedb.com pg_upgrade test writes to source directory]<br />
** Owner: Michael Paquier (322becb6085cb92d3708635eea61b45776bf27b6)<br />
** Fixed by: {{PgCommitURL|15b6d2155375dee2fcba072fffa03c1c8b44656c}}<br />
* [https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com pg_upgrade is not idempotent, even with --check]<br />
** Owner: Michael Paquier (38bfae36526636ef55daf7cf2a3282403587cb5b)<br />
** Fixed by: {{PgCommitURL|4fff78f00910af0137f9de7532f8eb21d08ab1c3}}<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|fd0b9dcebda7b931a41ce5c8e86d13f2efd0af2e}}<br />
* [https://www.postgresql.org/message-id/05ebcb44-f383-86e3-4f31-0a97a55634cf%40enterprisedb.com Ignoring BRIN for HOT udpates seems broken]<br />
** Owner: Tomas Vondra (5753d4ee320b)<br />
** Fixed by: {{PgCommitURL|e3fcca0d0d2414f3a50d6fd40eddf48b7df81475}}<br />
* [https://www.postgresql.org/message-id/PAXPR02MB760039506C87A2083AD85575E3DA9%40PAXPR02MB7600.eurprd02.prod.outlook.com psql no longer reports NOTICE messages promptly]<br />
** Owner: Peter Eisentraut (7844c9918)<br />
** Fixed by: {{PgCommitURL|e77de23fbb0f4ef27090c144edcfa889bb2a06d5}}<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
** Fixed by: {{PgCommitURL|e243de03fb4583dd4a9f0afb41493727d7946c02}}<br />
* [https://www.postgresql.org/message-id/20220607154744.vvmitnqhyxrne5ms%40jrouhaud COPY WITH (HEADER MATCH) broken with custom attribute list]<br />
** Owner: Peter Eisentraut (072132f04e55c1c3b0f1a582318da78de7334379)<br />
** Fixed by: {{PgCommitURL|ca7a0d1d368216e89359c63531a4df0b99a437e4}}<br />
* [https://www.postgresql.org/message-id/flat/DM4PR84MB17349C4E7D88A68264C18AF3EED69%40DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual]<br />
** Tomas Vondra<br />
** Fixed by: {{PgCommitURL|401f623c7b14890011b9bb9dda7639b1de4d40ad}}<br />
* [https://www.postgresql.org/message-id/20220625151930.GH22452@telsasoft.com Incorrect version check for datlocprovider in pg_upgrade]<br />
** Owner: Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|fa06a34d14ea053e1e405a6ab2a1c3f1631c3a5e}}<br />
* [https://www.postgresql.org/message-id/17522-bfcd5c603b5f4daa@postgresql.org Failure in TAP tests for IP address support in SANs with LibreSSL]<br />
** Owner: Peter Eisentraut (c1932e542863f0f646f005b3492452acc57c7e66)<br />
** Fixed by: {{PgCommitURL|901a9d53011573e45cd7b87682f0520ef3b0fd2d}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
== Won't Fix ==<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Problem showed by 90efa2f5565d28054c30c18f6a2f17f94fdff91e.<br />
* [https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de Reduce amount of logs generated by TAP tests of pg_upgrade?]<br />
** Owner: Michael Paquier<br />
** Other thread: [https://www.postgresql.org/message-id/YrP6ZRXITYWhpVrl@paquier.xyz here]<br />
** The problem is wider than just the upgrade tests, as all the runs of pg_regress would be impacted. We may want a more centralized solution for this older problem.<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: June 30, 2022<br />
* Beta 3: (August 11, 2022)<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37097PostgreSQL 15 Open Items2022-07-13T04:12:19Z<p>Davidrowley: Moved "PG15 beta1 sort performance regression due to Generation context change" to "Won't Fix"</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Owner: Andrew Dunstan (90efa2f5565d28054c30c18f6a2f17f94fdff91e), though the problem is much older than that and the addition of this test makes it to show up.<br />
* [https://www.postgresql.org/message-id/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de Revert debugging added due to 019_replslot_limit]<br />
** Owner: Andres Freund<br />
* [https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de Reduce amount of logs generated by TAP tests of pg_upgrade?]<br />
** Owner: Michael Paquier<br />
* [https://www.postgresql.org/message-id/20220616233130.rparivafipt6doj3%40alap3.anarazel.de PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size]<br />
** Owner: Andrew Dunstan<br />
* [https://www.postgresql.org/message-id/20220701231413.GI13040@telsasoft.com large objects lost on upgrade]<br />
** Owner: Robert Haas (9a974cbcba005256a19991203583a94b4f9a21a9)<br />
* [https://www.postgresql.org/message-id/20220706224727.GA2158260@nathanxps13 pg_parameter_aclcheck() and trusted extensions]<br />
** Owner: Tom Lane (a0ffa885e478f5eeacc4e250e35ce25a4740c487)<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Defaults:<br />
** [https://www.postgresql.org/message-id/flat/CALj2ACX-rW_OeDcp4gqrFUAkf1f50Fnh138dmkd0JkvCNQRKGA%40mail.gmail.com log_checkpoints, log_autovacuum_min_duration]<br />
*** [https://www.postgresql.org/message-id/618196db.1c69fb81.51c9a.00c1%40mx.google.com What about log_lock_waits, log_recovery_conflict_waits?]<br />
** [https://www.postgresql.org/message-id/20220216212952.GH31460@telsasoft.com initdb: default_toast_compression=lz4]<br />
** recovery_prefetch<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/f8a4105f076544c180a87ef0c4822352%40stmuk.bayern.de Extension pg_trgm, permissions and pg_dump order]<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
* [https://www.postgresql.org/message-id/17485-396609c6925b982d%40postgresql.org Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|e28bb885196916b0a3d898ae4f2be0e38108d81b}}<br />
<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|7201cd1862}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvrHQkiFRHiGiAS-LMOvJN-eK-s762=tVzBz8ZqUea-a_A@mail.gmail.com tuplesort Generation memory contexts don't play nicely with index builds]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|ae1123f9899fe80935ae344e38f18632beb1bf9a}}<br />
* [https://www.postgresql.org/message-id/YrpVkADAY0knF6vM@paquier.xyz Repeatability of installcheck for test_oat_hooks]<br />
** Owner: Andrew Dunstan<br />
** Fixed by: {{PgCommitURL|a6434b951558baad8372dc4b83bf87606dac9cda}}<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
** Fixed by: {{PgCommitURL|b4529005fd387e863bfa9eb863629b1183c0449c}}<br />
* [https://www.postgresql.org/message-id/f80ace33-11fb-1cd3-20f8-98f51d151088@enterprisedb.com pg_upgrade test writes to source directory]<br />
** Owner: Michael Paquier (322becb6085cb92d3708635eea61b45776bf27b6)<br />
** Fixed by: {{PgCommitURL|15b6d2155375dee2fcba072fffa03c1c8b44656c}}<br />
* [https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com pg_upgrade is not idempotent, even with --check]<br />
** Owner: Michael Paquier (38bfae36526636ef55daf7cf2a3282403587cb5b)<br />
** Fixed by: {{PgCommitURL|4fff78f00910af0137f9de7532f8eb21d08ab1c3}}<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|fd0b9dcebda7b931a41ce5c8e86d13f2efd0af2e}}<br />
* [https://www.postgresql.org/message-id/05ebcb44-f383-86e3-4f31-0a97a55634cf%40enterprisedb.com Ignoring BRIN for HOT udpates seems broken]<br />
** Owner: Tomas Vondra (5753d4ee320b)<br />
** Fixed by: {{PgCommitURL|e3fcca0d0d2414f3a50d6fd40eddf48b7df81475}}<br />
* [https://www.postgresql.org/message-id/PAXPR02MB760039506C87A2083AD85575E3DA9%40PAXPR02MB7600.eurprd02.prod.outlook.com psql no longer reports NOTICE messages promptly]<br />
** Owner: Peter Eisentraut (7844c9918)<br />
** Fixed by: {{PgCommitURL|e77de23fbb0f4ef27090c144edcfa889bb2a06d5}}<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
** Fixed by: {{PgCommitURL|e243de03fb4583dd4a9f0afb41493727d7946c02}}<br />
* [https://www.postgresql.org/message-id/20220607154744.vvmitnqhyxrne5ms%40jrouhaud COPY WITH (HEADER MATCH) broken with custom attribute list]<br />
** Owner: Peter Eisentraut (072132f04e55c1c3b0f1a582318da78de7334379)<br />
** Fixed by: {{PgCommitURL|ca7a0d1d368216e89359c63531a4df0b99a437e4}}<br />
* [https://www.postgresql.org/message-id/flat/DM4PR84MB17349C4E7D88A68264C18AF3EED69%40DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual]<br />
** Tomas Vondra<br />
** Fixed by: {{PgCommitURL|401f623c7b14890011b9bb9dda7639b1de4d40ad}}<br />
* [https://www.postgresql.org/message-id/20220625151930.GH22452@telsasoft.com Incorrect version check for datlocprovider in pg_upgrade]<br />
** Owner: Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|fa06a34d14ea053e1e405a6ab2a1c3f1631c3a5e}}<br />
* [https://www.postgresql.org/message-id/17522-bfcd5c603b5f4daa@postgresql.org Failure in TAP tests for IP address support in SANs with LibreSSL]<br />
** Owner: Peter Eisentraut (c1932e542863f0f646f005b3492452acc57c7e66)<br />
** Fixed by: {{PgCommitURL|901a9d53011573e45cd7b87682f0520ef3b0fd2d}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: June 30, 2022<br />
* Beta 3: TBD<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37089PostgreSQL 15 Open Items2022-07-06T20:19:54Z<p>Davidrowley: Resolved "tuplesort Generation memory contexts don't play nicely with index builds" issue</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Owner: Andrew Dunstan (90efa2f5565d28054c30c18f6a2f17f94fdff91e), though the problem is much older than that and the addition of this test makes it to show up.<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de Revert debugging added due to 019_replslot_limit]<br />
** Owner: Andres Freund<br />
* [https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de Reduce amount of logs generated by TAP tests of pg_upgrade?]<br />
** Owner: Michael Paquier<br />
* [https://www.postgresql.org/message-id/20220616233130.rparivafipt6doj3%40alap3.anarazel.de PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size]<br />
** Owner: Andrew Dunstan<br />
* [https://www.postgresql.org/message-id/YrpVkADAY0knF6vM@paquier.xyz Repeatability of installcheck for test_oat_hooks]<br />
** Owner: Andrew Dunstan<br />
* [https://www.postgresql.org/message-id/20220701231413.GI13040@telsasoft.com large objects lost on upgrade]<br />
** Owner: Robert Haas (9a974cbcba005256a19991203583a94b4f9a21a9)<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Defaults:<br />
** [https://www.postgresql.org/message-id/flat/CALj2ACX-rW_OeDcp4gqrFUAkf1f50Fnh138dmkd0JkvCNQRKGA%40mail.gmail.com log_checkpoints, log_autovacuum_min_duration]<br />
*** [https://www.postgresql.org/message-id/618196db.1c69fb81.51c9a.00c1%40mx.google.com What about log_lock_waits, log_recovery_conflict_waits?]<br />
** [https://www.postgresql.org/message-id/20220216212952.GH31460@telsasoft.com initdb: default_toast_compression=lz4]<br />
** recovery_prefetch<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/f8a4105f076544c180a87ef0c4822352%40stmuk.bayern.de Extension pg_trgm, permissions and pg_dump order]<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
* [https://www.postgresql.org/message-id/17485-396609c6925b982d%40postgresql.org Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|e28bb885196916b0a3d898ae4f2be0e38108d81b}}<br />
<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|7201cd1862}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvrHQkiFRHiGiAS-LMOvJN-eK-s762=tVzBz8ZqUea-a_A@mail.gmail.com tuplesort Generation memory contexts don't play nicely with index builds]<br />
** Owner: David Rowley<br />
** Fixed by: {{PgCommitURL|ae1123f9899fe80935ae344e38f18632beb1bf9a}}<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
** Fixed by: {{PgCommitURL|b4529005fd387e863bfa9eb863629b1183c0449c}}<br />
* [https://www.postgresql.org/message-id/f80ace33-11fb-1cd3-20f8-98f51d151088@enterprisedb.com pg_upgrade test writes to source directory]<br />
** Owner: Michael Paquier (322becb6085cb92d3708635eea61b45776bf27b6)<br />
** Fixed by: {{PgCommitURL|15b6d2155375dee2fcba072fffa03c1c8b44656c}}<br />
* [https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com pg_upgrade is not idempotent, even with --check]<br />
** Owner: Michael Paquier (38bfae36526636ef55daf7cf2a3282403587cb5b)<br />
** Fixed by: {{PgCommitURL|4fff78f00910af0137f9de7532f8eb21d08ab1c3}}<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|fd0b9dcebda7b931a41ce5c8e86d13f2efd0af2e}}<br />
* [https://www.postgresql.org/message-id/05ebcb44-f383-86e3-4f31-0a97a55634cf%40enterprisedb.com Ignoring BRIN for HOT udpates seems broken]<br />
** Owner: Tomas Vondra (5753d4ee320b)<br />
** Fixed by: {{PgCommitURL|e3fcca0d0d2414f3a50d6fd40eddf48b7df81475}}<br />
* [https://www.postgresql.org/message-id/PAXPR02MB760039506C87A2083AD85575E3DA9%40PAXPR02MB7600.eurprd02.prod.outlook.com psql no longer reports NOTICE messages promptly]<br />
** Owner: Peter Eisentraut (7844c9918)<br />
** Fixed by: {{PgCommitURL|e77de23fbb0f4ef27090c144edcfa889bb2a06d5}}<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
** Fixed by: {{PgCommitURL|e243de03fb4583dd4a9f0afb41493727d7946c02}}<br />
* [https://www.postgresql.org/message-id/20220607154744.vvmitnqhyxrne5ms%40jrouhaud COPY WITH (HEADER MATCH) broken with custom attribute list]<br />
** Owner: Peter Eisentraut (072132f04e55c1c3b0f1a582318da78de7334379)<br />
** Fixed by: {{PgCommitURL|ca7a0d1d368216e89359c63531a4df0b99a437e4}}<br />
* [https://www.postgresql.org/message-id/flat/DM4PR84MB17349C4E7D88A68264C18AF3EED69%40DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual]<br />
** Tomas Vondra<br />
** Fixed by: {{PgCommitURL|401f623c7b14890011b9bb9dda7639b1de4d40ad}}<br />
* [https://www.postgresql.org/message-id/20220625151930.GH22452@telsasoft.com Incorrect version check for datlocprovider in pg_upgrade]<br />
** Owner: Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|fa06a34d14ea053e1e405a6ab2a1c3f1631c3a5e}}<br />
* [https://www.postgresql.org/message-id/17522-bfcd5c603b5f4daa@postgresql.org Failure in TAP tests for IP address support in SANs with LibreSSL]<br />
** Owner: Peter Eisentraut (c1932e542863f0f646f005b3492452acc57c7e66)<br />
** Fixed by: {{PgCommitURL|901a9d53011573e45cd7b87682f0520ef3b0fd2d}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: June 30, 2022<br />
* Beta 3: TBD<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37087PostgreSQL 15 Open Items2022-07-06T01:34:05Z<p>Davidrowley: /* Open Issues */ Added tuplesort Generation memory contexts don't play nicely with index builds</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Owner: Andrew Dunstan (90efa2f5565d28054c30c18f6a2f17f94fdff91e), though the problem is much older than that and the addition of this test makes it to show up.<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de Revert debugging added due to 019_replslot_limit]<br />
** Owner: Andres Freund<br />
* [https://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de Reduce amount of logs generated by TAP tests of pg_upgrade?]<br />
** Owner: Michael Paquier<br />
* [https://www.postgresql.org/message-id/20220616233130.rparivafipt6doj3%40alap3.anarazel.de PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size]<br />
** Owner: Andrew Dunstan<br />
* [https://www.postgresql.org/message-id/YrpVkADAY0knF6vM@paquier.xyz Repeatability of installcheck for test_oat_hooks]<br />
** Owner: Andrew Dunstan<br />
* [https://www.postgresql.org/message-id/20220701231413.GI13040@telsasoft.com large objects lost on upgrade]<br />
** Owner: Robert Haas (9a974cbcba005256a19991203583a94b4f9a21a9)<br />
* [https://www.postgresql.org/message-id/CAApHDvrHQkiFRHiGiAS-LMOvJN-eK-s762=tVzBz8ZqUea-a_A@mail.gmail.com tuplesort Generation memory contexts don't play nicely with index builds]<br />
** Owner: David Rowley<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Defaults:<br />
** [https://www.postgresql.org/message-id/flat/CALj2ACX-rW_OeDcp4gqrFUAkf1f50Fnh138dmkd0JkvCNQRKGA%40mail.gmail.com log_checkpoints, log_autovacuum_min_duration]<br />
*** [https://www.postgresql.org/message-id/618196db.1c69fb81.51c9a.00c1%40mx.google.com What about log_lock_waits, log_recovery_conflict_waits?]<br />
** [https://www.postgresql.org/message-id/20220216212952.GH31460@telsasoft.com initdb: default_toast_compression=lz4]<br />
** recovery_prefetch<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/f8a4105f076544c180a87ef0c4822352%40stmuk.bayern.de Extension pg_trgm, permissions and pg_dump order]<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
* [https://www.postgresql.org/message-id/17485-396609c6925b982d%40postgresql.org Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|e28bb885196916b0a3d898ae4f2be0e38108d81b}}<br />
<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Affects v14<br />
** Fixed by: {{PgCommitURL|7201cd1862}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
** Fixed by: {{PgCommitURL|b4529005fd387e863bfa9eb863629b1183c0449c}}<br />
* [https://www.postgresql.org/message-id/f80ace33-11fb-1cd3-20f8-98f51d151088@enterprisedb.com pg_upgrade test writes to source directory]<br />
** Owner: Michael Paquier (322becb6085cb92d3708635eea61b45776bf27b6)<br />
** Fixed by: {{PgCommitURL|15b6d2155375dee2fcba072fffa03c1c8b44656c}}<br />
* [https://www.postgresql.org/message-id/77e6ecaa-2785-97aa-f229-4b6e047cbd2b@enterprisedb.com pg_upgrade is not idempotent, even with --check]<br />
** Owner: Michael Paquier (38bfae36526636ef55daf7cf2a3282403587cb5b)<br />
** Fixed by: {{PgCommitURL|4fff78f00910af0137f9de7532f8eb21d08ab1c3}}<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
** Fixed by: {{PgCommitURL|fd0b9dcebda7b931a41ce5c8e86d13f2efd0af2e}}<br />
* [https://www.postgresql.org/message-id/05ebcb44-f383-86e3-4f31-0a97a55634cf%40enterprisedb.com Ignoring BRIN for HOT udpates seems broken]<br />
** Owner: Tomas Vondra (5753d4ee320b)<br />
** Fixed by: {{PgCommitURL|e3fcca0d0d2414f3a50d6fd40eddf48b7df81475}}<br />
* [https://www.postgresql.org/message-id/PAXPR02MB760039506C87A2083AD85575E3DA9%40PAXPR02MB7600.eurprd02.prod.outlook.com psql no longer reports NOTICE messages promptly]<br />
** Owner: Peter Eisentraut (7844c9918)<br />
** Fixed by: {{PgCommitURL|e77de23fbb0f4ef27090c144edcfa889bb2a06d5}}<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
** Fixed by: {{PgCommitURL|e243de03fb4583dd4a9f0afb41493727d7946c02}}<br />
* [https://www.postgresql.org/message-id/20220607154744.vvmitnqhyxrne5ms%40jrouhaud COPY WITH (HEADER MATCH) broken with custom attribute list]<br />
** Owner: Peter Eisentraut (072132f04e55c1c3b0f1a582318da78de7334379)<br />
** Fixed by: {{PgCommitURL|ca7a0d1d368216e89359c63531a4df0b99a437e4}}<br />
* [https://www.postgresql.org/message-id/flat/DM4PR84MB17349C4E7D88A68264C18AF3EED69%40DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM PG15 beta1 fix pg_stats_ext/pg_stats_ext_exprs view manual]<br />
** Tomas Vondra<br />
** Fixed by: {{PgCommitURL|401f623c7b14890011b9bb9dda7639b1de4d40ad}}<br />
* [https://www.postgresql.org/message-id/20220625151930.GH22452@telsasoft.com Incorrect version check for datlocprovider in pg_upgrade]<br />
** Owner: Peter Eisentraut (f2553d43060edb210b36c63187d52a632448e1d2)<br />
** Fixed by: {{PgCommitURL|fa06a34d14ea053e1e405a6ab2a1c3f1631c3a5e}}<br />
* [https://www.postgresql.org/message-id/17522-bfcd5c603b5f4daa@postgresql.org Failure in TAP tests for IP address support in SANs with LibreSSL]<br />
** Owner: Peter Eisentraut (c1932e542863f0f646f005b3492452acc57c7e66)<br />
** Fixed by: {{PgCommitURL|901a9d53011573e45cd7b87682f0520ef3b0fd2d}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: June 30, 2022<br />
* Beta 3: TBD<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=37001PostgreSQL 15 Open Items2022-05-26T22:47:20Z<p>Davidrowley: Mark "Regression in 15beta1 when filtering subquery including row_number window function" as fixed</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Owner: Andrew Dunstan (90efa2f5565d28054c30c18f6a2f17f94fdff91e)<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
* [https://www.postgresql.org/message-id/20220519193839.GT19626%40telsasoft.com -c min_dynamic_shared_memory now triggers an assertion]<br />
** Owner: Thomas Munro ?<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Defaults: log_checkpoints, log_lock_waits, log_recovery_conflict_waits, default_toast_compression, recovery_prefetch<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
** Fixed by: {{PgCommitURL|3e9abd2eb1b1f6863250f060290f514f30ce8044}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: TBD<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=36965PostgreSQL 15 Open Items2022-05-25T02:16:33Z<p>Davidrowley: /* Open Issues */ Added owner of row_number window function regression</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Owner: Andrew Dunstan (90efa2f5565d28054c30c18f6a2f17f94fdff91e)<br />
* [https://www.postgresql.org/message-id/202204251548.mudq7jbqnh7r@alvherre.pgsql bogus: logical replication rows/cols combinations]<br />
** Owner: Amit Kapila<br />
* [https://www.postgresql.org/message-id/20220517.162719.1671558681467343711.horikyota.ntt@gmail.com amcheck is using a wrong macro to check compressed-ness]<br />
** Owner: Robert Haas (bd807be6935929bdefe74d1258ca08048f0aafa3)<br />
* [https://www.postgresql.org/message-id/CAApHDvqXpLzav6dUeR5vO_RBh_feHrHMLhigVQXw9jHCyKP9PA%40mail.gmail.com PG15 beta1 sort performance regression due to Generation context change]<br />
** Owner: David Rowley<br />
* [https://www.postgresql.org/message-id/20220524235250.gtt3uu5zktfkr4hv@alap3.anarazel.de Safety of subtrans ID caching]<br />
** Owner: Michael Paquier (06f5295af673df795e8e70e28c43d61c2817b6df)<br />
* [https://www.postgresql.org/message-id/17495-7ffe2fa0b261b9fa@postgresql.org Regression in 15beta1 when filtering subquery including row_number window function]<br />
** Owner: David Rowley (9d9c02ccd1aea8e9131d8f4edb21bf1687e40782)<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Defaults: log_checkpoints, log_lock_waits, log_recovery_conflict_waits, default_toast_compression, recovery_prefetch<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGK3PGKwcKqzoosamn36YW-fsuTdOPPF1i_rtEO%3DnEYKSg%40mail.gmail.com RecoveryConflictInterrupt() is unsafe in a signal handler]<br />
** This seems to [https://www.postgresql.org/message-id/447238.1651082925%40sss.pgh.pa.us explain buildfarm failures in 031_recovery_conflict.pl]<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TOAST fetches could perhaps occur after the needed data has been removed]<br />
** The symptom originally reported in the thread was fixed by {{PgCommitURL|9f4f0a0dad4c7422a97d94e4051c08ec6d181dd6}}, but nobody is very happy with the status quo in this area. Do we need to do more now?<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
** Fixed by: {{PgCommitURL|8ab0ebb9a842dc6063d1374a38b47a3b7ee64afe}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 15beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CA+HiwqGAGobiiHR8nH382HJxqm1mzZs8=3oKPXnXivWoFSZmNA@mail.gmail.com pgbench --partitions=0]<br />
** Owner; Michael Paquier (6f164e6d17616a157ea5d9e34dbb1b211c080c41)<br />
** Fixed by: {{PgCommitURL|27f1366050c6cd8c1ea5f03b367a5a167ebf34b7}}<br />
* [https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us psql now shows zero elapsed time after an error]<br />
** Owner: Peter Eisentraut<br />
** Fixed by: {{PgCommitURL|9520f8d92a8681e441cc863422babd544353dd39}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/de57761c-b99b-3435-b0a6-474c72b1149a%40enterprisedb.com libpq: duplicate error message after connection loss]<br />
** Fixed by: {{PgCommitURL|93909599cdba64c8759d646983c0a4ef93de1e50}}<br />
<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Fixed by: {{PgCommitURL|ce4f46fdc814eb1b704d81640f6d8f03625d0f53}}<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKFQuwamFuaQHKdhcMt4Gbw5+Hca2UE741B8gOOXoA=TtAd2Yw@mail.gmail.com Incorrect reset timestamp in stats after crash recovery]<br />
** Owner: Andres Freund (5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd)<br />
** Fixed at: {{PgCommitURL|5cd1c40b3ce9600f129fd1fea9850e1affaf31d5}}<br />
<br />
* [https://www.postgresql.org/message-id/YlPQGNAAa04raObK@paquier.xyz Fixes for compression options of pg_receivewal and refactoring of backup_compression.{c,h}]<br />
** Owner: Michael Paquier (babbbb595d2322da095a1e6703171b3f1f2815cb)<br />
** Fixed at: {{PgCommitURL|042a923ad53dfbe39a9d5012d6c3cf3c9c338884}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Owner: Michael Paquier (46dea2419ee7895a4eb3d048317682e6f18a17e1)<br />
** Fixed at: {{PgCommitURL|e61efafcb82c605dcc78f668685223e20d2f7ad8}}, {{PgCommitURL|1a8b110539efe18803c1fa8aa452a2178dbad9a9}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
** Fixed at: {{PgCommitURL|99c754129d787ea4ce3b34b9f4c5f5e74c45ab6a}}<br />
<br />
* [https://www.postgresql.org/message-id/YlZyp26LVVfmwfgW@paquier.xyz Small issues with CLUSTER on partitioned tables]<br />
** Owner: Alvaro Herrera (cfdd03f45e6afc632fbe70519250ec19167d6765)<br />
** Fixed at: {{PgCommitURL|3f19e176ae0f55a653d62e1504dbe5ad8c1006a0}}, {{PgCommitURL|21a10368eb3fce73f146d7e48b4d81496f60d965}}<br />
<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
** Fixed at: {{PgCommitURL|5c854e7a2c8a6cd26040e0f9949e7a4a007f6366}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20220209220004.kb3dgtn2x2k2gtdm%40alap3.anarazel.de Corruption due to relfilenode reuse]<br />
** pg_upgrade can corrupt data with the new OIDs preservation feature<br />
*** Fixed at: {{PgCommitURL|e2f65f42555ff531c6d7c8f151526b4ef7c016f8}}<br />
** the ProcSignalBarrier solution this builds on also turns out to have a small race/hole<br />
*** Fixed at: {{PgCommitURL|b74e94dc27fdbb13954f230b1d1298430afa6c0c}}<br />
** Owner: Thomas Munro, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20220502042718.GB1565149@rfd.leadboat.com Some issues with the TAP tests of pg_upgrade]<br />
** Owner: Michael Paquier<br />
** Fixed at: {{PgCommitURL|7dd3ee508432730d15c5d3032f37362f6b6e4dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMbWs4-LN%3DbF8f9eU2R94dJtF54DfDvBq%2BovqHnOQqbinYDrUw%40mail.gmail.com Crash in _outPathTarget]<br />
** Owner: Peter Eisentraut<br />
** Fixed at: {{PgCommitURL|9ddf251f94090cebf1bd8fc18396cb8a4b580d04}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/Ymd/e5eeZMNAkrXo%40paquier.xyz#23885a148c6899cc874a7bf68f228777 Instability of regression test of pg_walinspect]<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|ed57cac84d1c5642737dab1e4c4b8cb4f0c4305f}}<br />
<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
** Fixed at: {{PgCommitURL|4eb9798879680dcc0e3ebb301cf6f925dfa69422}}, {{PgCommitURL|112fdb3528465cc14a2f1dff3dc27f100326d885}}<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1LpBFU49Ohbnk%3Ddv_v9YP%2BKqh1%2BSf8i%2B%2B_s-QhD1Gy4Qw%40mail.gmail.com 013_partition.pl failing]<br />
** Fixed at: {{PgCommitURL|dd4ab6fd6528e160571986fa8817cee9f2645aa8}}<br />
<br />
* [https://www.postgresql.org/message-id/Yni6ZHkGotUU+RSf@paquier.xyz Avoid garbage logs with postgres -C on runtime-computed GUCs]<br />
** Fixed at: {{PgCommitURL|8bbf8461a3a2a38ce5f2952a025385b6938a61f7}}<br />
** Owner: Michael Paquier<br />
<br />
* [https://www.postgresql.org/message-id/20220506234924.6mxxotl3xl63db3l@alap3.anarazel.de Some issues with mark_pgdllimport.pl]<br />
** Fixed at: {{PgCommitURL|5edeb574285ecbcc47f0b769a7e363404db0155b}}<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/1656446.1650043715%40sss.pgh.pa.us Crash in new pgstats code]<br />
** Initially reported issue was fixed by {{PgCommitURL|4a736a161c306fcfed970e6b649f2f03f465ac24}}, but there may be more to do here.<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/b3463b8c-2328-dcac-0136-af95715493c1%40xs4all.nl TRAP: FailedAssertion("tabstat->trans == trans", File: "pgstat_relation.c", Line: 508]<br />
** Fixed at: {{PgCommitURL|0cf16cb8ca4853b084c40eca310c4c9c3ebf7e2a}}<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Fixed at: {{PgCommitURL|4f2400cb3f10aa79f99fba680c198237da28dd38}}, {{PgCommitURL|ab02d702ef08343fba30d90fdf7df5950063e8c9}}, {{PgCommitURL|7fc0e7de9fb8306e84d1c15211aba4308f694455}}<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: May 19, 2022<br />
* Beta 2: TBD<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_15_Open_Items&diff=36834PostgreSQL 15 Open Items2022-04-11T00:24:11Z<p>Davidrowley: /* Open Issues */ Added qsort performance regression item</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* InvokeNamespaceSearchHook calls need to be moved<br />
** [https://www.postgresql.org/message-id/2600348.1647987525%40sss.pgh.pa.us Re: New Object Access Type hooks]<br />
** Owner: Andrew Dunstan (90efa2f5565d28054c30c18f6a2f17f94fdff91e)<br />
* Snapshot assertion in init_toast_snapshot()<br />
** [https://www.postgresql.org/message-id/flat/dc9dd229-ed30-6c62-4c41-d733ffff776b%40xs4all.nl TRAP: FailedAssertion("HaveRegisteredOrActiveSnapshot()"]<br />
** Owner: Andres Freund (2776922201f751e3202a713b61d97fe4e44a8440)<br />
* [https://www.postgresql.org/message-id/YkfeMNYRCGhySKyg%40ahch-to crash with JSON constructors and window functions]<br />
** Owner: Andrew Dunstan (f4fb45d15c59d7add2e1b81a9d477d0119a9691a)<br />
* [https://www.postgresql.org/message-id/fab3b90a-914d-46a9-beb0-df011ee39ee5%40www.fastmail.com MERGE: ERROR: variable not found in subplan target lists]<br />
** Owner: Alvaro Herrera (7103ebb7aae8ab8076b7e85f335ceb8fe799097c)<br />
* [https://www.postgresql.org/message-id/2976736.1649218027%40sss.pgh.pa.us Why is 013_partition.pl failing?]<br />
* [https://www.postgresql.org/message-id/20220408124338.GK24419@telsasoft.com asynchronous execution crash in trivial_subqueryscan()]<br />
** Owner: Etsuro Fujita (c2bb02bc2e858ba345b8b33f1f3a54628f719d93)<br />
* [https://www.postgresql.org/message-id/4015413.1649454951%40sss.pgh.pa.us Timing-dependent failure in 002_archiving.pl]<br />
** Not clear if this is the test's fault or a bug in 5dc0418fab<br />
* [https://www.postgresql.org/message-id/YlGJGiofZiWN3elx@jrouhaud limitations of GetMaxBackends()]<br />
** Owner: Robert Haas (aa64f23b02924724eafbd9eadbf26d85df30a12b, and 4567596316d186c6e61c72df013797266fcac2f7)<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRbzaAOUtBUcjF5hLtaSHnJUqXmtiaLEoi53zeWSizeA@mail.gmail.com qsort performance regression]<br />
** Owner: John Naylor (6974924347c908335607a4a2f252213d58e21b7c)<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* Defaults: log_checkpoints, log_lock_waits, log_recovery_conflict_waits, default_toast_compression<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEze2WgGiw%2BLZt%2BvHf8tWqB_6VxeLsMeoAuod0N%3Dij1q17n5pw%40mail.gmail.com Non-replayable WAL records through overflows and >MaxAllocSize lengths]<br />
** In other words; we can write xlog records that we can't read (plus potentially actual WAL corruption); making the instance unrecoverable, and blocks any replication.<br />
** Exploitation seems limited to WAL records of 2PC and logical replication, and extension-generated WAL.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn22s42h4Lh6v96GsXSKGd%3D_6b76mjqip_WFCGnBmTJCw%40mail.gmail.com CLUSTER sort on abbreviated expressions is broken]<br />
** Affects all stable branches.<br />
<br />
=== Fixed issues ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com Remove compatibility from pg_basebackup?]<br />
** Fixed at: {{PgCommitURL|9cd28c2e5f11dfeef64a14035b82e70acead65fd}}<br />
<br />
=== resolved before 15beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20220212211316.GK31460%40telsasoft.com Buildfarm warnings]<br />
** pg_basebackup.c:1261:35: warning: storing the address of local variable archive_filename in progress_filename [-Wdangling-pointer=]<br />
** new in 23a1c6578 - looks like a real error @Robert Haas<br />
** Fixed at: {{PgCommitURL|62cb7427d1e491faf8612a82c2e3711a8cd65422}}<br />
<br />
* [https://www.postgresql.org/message-id/20220311010223.GI28503@telsasoft.com pg_basebackup serverside compression broken with stdout and manifests]<br />
** Fixed at: {{PgCommitURL|b2de45f9200d9adcac50015521574696dc464ccd}}<br />
<br />
* pg_basebackup: bbstreamer_lz4.c:172: bbstreamer_lz4_compressor_content: Assertion `mystreamer->base.bbs_buffer.maxlen >= out_bound' failed. <br />
** [https://www.postgresql.org/message-id/20220316151253.GB28503@telsasoft.com basebackup LZ4 to stdout]<br />
** Owner: Robert Haas (dab298471ff2f91f33bc25bfb73e435d3ab02148)<br />
** Fixed at: {{PgCommitURL|afb529e6772b4e2b065644a2204697eeaf6c9a96}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2022 ('''Last Day to Commit Features''')<br />
* Beta 1: TBD<br />
* GA: TBD<br />
<br />
== See also ==<br />
<br />
* [[Release Management Team]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=Committing_checklist&diff=36226Committing checklist2021-07-01T01:28:37Z<p>Davidrowley: /* Basic */ Add mention about using the first 9 chars of commit SHAs to reference other commits.</p>
<hr />
<div>This document is an attempt to list common checks that PostgreSQL project [[Committers]] may want to adopt as part of a checklist of things to check before pushing. There are certain classic mistakes that even experienced committers have been known to make occasionally. In the real world, many mistakes happen when a step is skipped over during a routine process, perhaps caused by a seemingly insignificant last minute change. It's important to learn from these mistakes.<br />
<br />
This checklist isn't intended as something that committers will adopt wholesale. Rather, it is intended as a starting point for creating your own semi-customized checklist. Since your final checklist is supposed to be used more or less mechanically, it shouldn't ever be too long, and should be organized into sections to make it easier to skip items where irrelevant. In short, if it's worth adopting something as a standard practice that you return to again and again, it's probably also worth writing that down, to formalize it. Use discretion when deciding what makes sense for you.<br />
<br />
= Basic checks =<br />
<br />
* Double-check release build compiler warnings.<br />
<br />
* make check-world.<br />
** You may want to speed this up by using the following recipe:<br />
make -j16 -s install;make -Otarget -j10 -s check-world && echo "quick make-check world success" || echo "quick make-check world failure"<br />
<br />
(Note that the recipe only works on REL_10_STABLE and later release branches, because test_decoding and a few other things fail.)<br />
<br />
* Consider the need for a catversion bump.<br />
<br />
* Don't assume that you haven't broken the doc build if you make even a trivial doc change.<br />
** Removing a GUC can break instances in the release notes where they're referenced. <br />
** Even grep can miss this, since references to the GUC will have dashes rather than underscores, plus possibly other variations.<br />
<br />
* Validate err*() calls against https://www.postgresql.org/docs/devel/static/error-style-guide.html<br />
<br />
* Validate *printf calls for trailing newlines.<br />
<br />
* Spellcheck the patch.<br />
<br />
* Verify that long lines are not better broken into several shorter lines:<br />
git diff origin/master | grep -E '^(\+|diff)' | sed 's/^+//' | expand -t4 | awk "length > 78 || /^diff/"<br />
<br />
* Run pgindent, pgperltidy, and reformat-dat-files on changed files; keep the changes minimal.<br />
<br />
* Run pgperlcritic on modified Perl files.<br />
<br />
* Update version numbers, if needed:<br />
CATALOG_VERSION_NO, PG_CONTROL_VERSION, XLOG_PAGE_MAGIC, PGSTAT_FILE_FORMAT_ID<br />
<br />
= Regression test checks =<br />
<br />
* When adding tests files, make sure that they're added to both serial and parallel schedules.<br />
<br />
* Look for alternative output files for any regression test you're updating the output of.<br />
** Some tests have alternative output files to work around portability issues.<br />
** Most of the time it works to just apply the same patch to the other variants as the delta you're observing for the output file that's relevant to your own platform.<br />
** Occasionally you may have to just see what the buildfarm says.<br />
<br />
= Git checks =<br />
<br />
== Basic ==<br />
<br />
* Do a dry run before really pushing by using --dry-run.<br />
<br />
* Look at "git status"; anything missing?<br />
<br />
* Author and committer timestamps should match.<br />
<br />
This can be an issue if you're in the habit of rebasing, or apply a patch with "git am". Make sure that your setup displays both in "git log", by specifying "--pretty=fuller", or changing the git format config. The easiest way to make both timestamps match is to amend the commit like so:<br />
<br />
git commit --amend --reset-author<br />
<br />
If you have "autosetuprebase = always" in your git config, then a last minute "git pull" could cause a rebase, which could cause author and committer timestamps to diverge a bit. In practice, small differences between author and committer timestamp are not considered to be a problem.<br />
<br />
* Write log message:<br />
Discussion: https://postgr.es/m/XXXXXXXXXXX<br />
Back-patch depth?<br />
What should the release notes say?<br />
Credit any reviewer.<br />
<br />
* When making references to other commits, it's a good idea to use the first 9 chars of the commit SHA. Fewer than 9 means there will be no hyperlink in the HTTP interface. More than 9 is not required.<br />
<br />
* Note compatibility issues in commit message, so that they'll get picked up later, when release notes are written.<br />
<br />
* Check merge with master (not applicable to commits).<br />
<br />
* If you're using a dedicated ssh key with a passphrase, you may find it useful to deliberately disable it when you're done pushing:<br />
<br />
$ ssh-add -d ~/.ssh/id_rsa_postgres<br />
<br />
== Backpatching and git ==<br />
<br />
Commit messages for multiple branches should be identical when back-patching, in order to have tooling recognize the redundancy for purposes of compiling release notes, and other things of that nature.<br />
<br />
* Easiest way to get commit metadata consistent is to not worry about commit messages outside of the master branch at first. Commit message on backbranches could initially be something like "pending 9.6".<br />
<br />
* Perform the following procedure on each back branch when you're done, by checking out each individual branch in gitmaster local clone, and doing this for master branch commit which has good commit message:<br />
<br />
git commit --amend --reset-author -C <commit><br />
<br />
You now have the same commit message on each branch. This means that the <code>src/tools/git_changelog</code> utility script will present the commits from each affected local branch together, as one logical change. (This script is used as a starting point when writing back branch release notes. Note that the concept of "one logical change" is not a standard git concept.)<br />
<br />
* Use <code>git push origin : --dry-run</code> to dry-run pushing all branches at once. Once satisfied, remove --dry-run to actually push. --dry-run is doubly important if you push each branch individually.<br />
<br />
= Maintaining ABI compatibility while backpatching =<br />
<br />
Avoid breaking ABI compatibility. It's unacceptable for extensions built against an earlier point release to break in a more recent point release.<br />
<br />
* You can only really change the signature of a function with local linkage, perhaps with a few rare exceptions.<br />
* You cannot modify any struct definition in src/include/*. If any new members must be added to a struct, put them at the end in backbranches. It's okay to have a different struct layout in master. Even then, extensions that allocate the struct can break via a dependency on its size.<br />
* Move new enum values to the end.<br />
<br />
See [https://postgr.es/m/1315116.1603900649@sss.pgh.pa.us this message] for more considerations on ABI preservation.<br />
<br />
= GUC checks =<br />
<br />
* When adding a new GUC, postgresql.conf.sample needs to be updated, too.<br />
<br />
* Is the GUC group the right one?<br />
<br />
= Advanced smoke tests =<br />
<br />
* Valgrind memcheck + "make installcheck".<br />
<br />
* CLOBBER_CACHE_ALWAYS.<br />
<br />
* When doing anything that touches WAL-logging, consider creating a replica, and making sure that wal_consistency_checking=all passes on replica while master runs "make installcheck". WAL_DEBUG makes any bug that this throws up easier to isolate.<br />
<br />
* "#define COPY_PARSE_PLAN_TREES" and "#define WRITE_READ_PARSE_PLAN_TREES" can catch omissions or other mistakes when "src/backend/nodes/*" were changed.<br />
<br />
* Various tests that are only run on certain platforms, enabled [https://www.postgresql.org/docs/devel/regress-run.html using PG_TEST_EXTRA or EXTRA_TESTS environment variables]. For example, PG_TEST_EXTRA='ssl' and EXTRA_TESTS='collate.linux.utf8' tests.</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36051PostgreSQL 14 Open Items2021-05-25T04:20:52Z<p>Davidrowley: Mark "EXPLAIN can suffer from cannot decompile join alias var in plan tree" as fixed.</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Owner: Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Owner: Peter Geoghegan<br />
** [https://www.postgresql.org/message-id/YJzU8wmVE0+TGAVP@paquier.xyz Patch]<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_resetwal]<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us CALL versus procedures with output-only arguments]<br />
** Owner: Peter Eisentraut<br />
** [https://www.postgresql.org/message-id/1157704.1621889070%40sss.pgh.pa.us Patch]<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
<br />
* [https://www.postgresql.org/message-id/4aa370cb91ecf2f9885d98b80ad1109c%40postgrespro.ru Add PortalDrop in exec_execute_message]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
** Fixed at: {{PgCommitURL|f21fadafaf0fb5ea4c9622d915972651273d62ce}} and {{PgCommitURL|84f5c2908dad81e8622b0406beea580e40bb03ac}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Fixed at {{PgCommitURL|cafde58b33}} and {{PgCommitURL|354f32d01d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Fixed at {{PgCommitURL|9e215378d7fbb7d4615be917917c52f246cc6c61}}<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Fixed at {{PgCommitURL|f5024d8d7b04de2f5f4742ab433cc38160354861}}<br />
<br />
* [https://www.postgresql.org/message-id/17030-5844aecae42fe223@postgresql.org EXPLAIN can suffer from cannot decompile join alias var in plan tree]<br />
** Fixed at {{PgCommitURL|cba5c70b956810c61b3778f7041f92fbb8065acb}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36048PostgreSQL 14 Open Items2021-05-24T02:19:15Z<p>Davidrowley: /* Open Issues */ Add reference to bug 17030</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Owner: Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Owner: Peter Geoghegan<br />
** [https://www.postgresql.org/message-id/YJzU8wmVE0+TGAVP@paquier.xyz Patch]<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_resetwal]<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Owner: Andres Freund, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us CALL versus procedures with output-only arguments]<br />
** Owner: Peter Eisentraut<br />
<br />
* [https://www.postgresql.org/message-id/17030-5844aecae42fe223@postgresql.org EXPLAIN can suffer from cannot decompile join alias var in plan tree]<br />
** Owner: David Rowley<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
<br />
* [https://www.postgresql.org/message-id/4aa370cb91ecf2f9885d98b80ad1109c%40postgrespro.ru Add PortalDrop in exec_execute_message]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
** Fixed at: {{PgCommitURL|f21fadafaf0fb5ea4c9622d915972651273d62ce}} and {{PgCommitURL|84f5c2908dad81e8622b0406beea580e40bb03ac}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Fixed at {{PgCommitURL|cafde58b33}} and {{PgCommitURL|354f32d01d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Fixed at {{PgCommitURL|9e215378d7fbb7d4615be917917c52f246cc6c61}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36029PostgreSQL 14 Open Items2021-05-22T06:55:39Z<p>Davidrowley: Mark "Result Cache works incorrectly with unique joins" as fixed</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Owner: Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Owner: Peter Geoghegan<br />
** [https://www.postgresql.org/message-id/YJzU8wmVE0+TGAVP@paquier.xyz Patch]<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_resetwal]<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Owner: Andres Freund, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us CALL versus procedures with output-only arguments]<br />
** Owner: Peter Eisentraut<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
<br />
* [https://www.postgresql.org/message-id/4aa370cb91ecf2f9885d98b80ad1109c%40postgrespro.ru Add PortalDrop in exec_execute_message]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
** Fixed at: {{PgCommitURL|f21fadafaf0fb5ea4c9622d915972651273d62ce}} and {{PgCommitURL|84f5c2908dad81e8622b0406beea580e40bb03ac}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Fixed at {{PgCommitURL|cafde58b33}} and {{PgCommitURL|354f32d01d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Fixed at {{PgCommitURL|9e215378d7fbb7d4615be917917c52f246cc6c61}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36021PostgreSQL 14 Open Items2021-05-21T00:02:35Z<p>Davidrowley: /* Open Issues */ Added Result Cache works incorrectly with unique joins item</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Owner: Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Owner: Peter Geoghegan<br />
** [https://www.postgresql.org/message-id/YJzU8wmVE0+TGAVP@paquier.xyz Patch]<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Owner: Bruce Momjian<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_resetwal]<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Owner: Andres Freund, Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us CALL versus procedures with output-only arguments]<br />
** Owner: Peter Eisentraut<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Owner: David Rowley<br />
** [https://www.postgresql.org/message-id/CAApHDvrWsfc3naVQZxS0efU%3DvJOA7dG3NV7fGhkgo2%3DJ38OEpg%40mail.gmail.com Patch]<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=Tuning_Your_PostgreSQL_Server&diff=35856Tuning Your PostgreSQL Server2021-03-31T09:47:26Z<p>Davidrowley: /* shared_buffers */ Remove mention about using smaller shared buffers on windows. This was removed from the docs in 81c5272. Let's remove it here too.</p>
<hr />
<div>__NOTOC__<br />
''by Greg Smith, Robert Treat, and Christopher Browne''<br />
<br />
{{Languages}}<br />
<br />
PostgreSQL ships with a basic configuration tuned for wide compatibility rather than performance. Odds are good the default parameters are very undersized for your system. Rather than get dragged into the details of everything you should eventually know (which you can find if you want it at the [http://www.pgcon.org/2008/schedule/events/104.en.html GUC Three Hour Tour]), here we're going to sprint through a simplified view of the basics, with a look at the most common things people new to PostgreSQL aren't aware of. You should click on the name of the parameter in each section to jump to the relevant documentation in the PostgreSQL manual for more details after reading the quick intro here. There is also additional information available about many of these parameters, as well as a list of parameters you shouldn't adjust, at [https://www.packtpub.com/article/server-configuration-tuning-postgresql Server Configuration Tuning].<br />
<br />
== Background Information on Configuration Settings ==<br />
<br />
PostgreSQL settings can be manipulated a number of different ways, but generally you will want them changed in your configuration files, either directly or, starting with PostgreSQL 9.4, through [http://www.postgresql.org/docs/current/static/sql-altersystem.html <tt>ALTER SYSTEM</tt>]. The specific options available change from release to release, the definitive list is in the source code at src/backend/utils/misc/guc.c for your version of PostgreSQL (but the pg_settings view works well enough for most purposes).<br />
<br />
=== The types of settings ===<br />
<br />
There are several different types of configuration settings, divided up based on the possible inputs they take<br />
<br />
* Boolean: true, false, on, off<br />
* Integer: Whole numbers (2112)<br />
* Float: Decimal values (21.12)<br />
* Memory / Disk: Integers (2112) or "computer units" (512MB, 2112GB). Avoid integers--you need to know the underlying unit to figure out what they mean.<br />
* Time: "Time units" aka d,m,s (30s). Sometimes the unit is left out; don't do that<br />
* Strings: Single quoted text ('pg_log')<br />
* ENUMs: Strings, but from a specific list ('WARNING', 'ERROR')<br />
* Lists: A comma separated list of strings ('"$user",public,tsearch2) <br />
<br />
=== When they take effect ===<br />
<br />
PostgreSQL settings have different levels of flexibility for when they can be changed, usually related to internal code restrictions. The complete list of levels is:<br />
<br />
* Postmaster: requires restart of server <br />
* Sighup: requires a HUP of the server, either by kill -HUP (usually -1), pg_ctl reload, or <tt>SELECT pg_reload_conf()</tt>;<br />
* User: can be set within individual sessions, take effect only within that session<br />
* Internal: set at compile time, can't be changed, mainly for reference<br />
* Backend: settings which must be set before session start<br />
* Superuser: can be set at runtime for the server by superusers<br />
<br />
Most of the time you'll only use the first of these, but the second can be useful if you have a server you don't want to take down, while the user session settings can be helpful for some special situations. You can tell which type of parameter a setting is by looking at the "context" field in the pg_settings view.<br />
<br />
=== Important notes about configuration files ===<br />
<br />
* Command line options override postgresql.auto.conf settings override postgresql.conf settings.<br />
* If the same setting is listed multiple times, the last one wins.<br />
* You can figure out the postgresql.conf location with <tt>SHOW config_file</tt>. It will generally be $PGDATA/postgresql.conf (<tt>SHOW data_directory</tt>), but watch out for symbolic links, [http://www.postgresql.org/docs/current/static/app-pg-ctl.html#AEN93617 postmaster.opts] and other trickiness<br />
* Lines with # are comments and have no effect. For a new database, this will mean the setting is using the default, but on running systems this may not hold true! Changes to the configuration files do not take effect without a reload/restart, so it's possible for the system to be running something different from what is in the file. <br />
<br />
=== Viewing the current settings === <br />
<br />
* Look at the configuration files. This is generally not definitive!<br />
* <tt>SHOW ALL</tt>, <tt>SHOW <setting></tt> will show you the current value of the setting. Watch out for session specific changes<br />
* <tt>SELECT * FROM pg_settings</tt> will label session specific changes as locally modified<br />
<br />
=== Tuning tools ===<br />
<br />
* [https://www.devart.com/dbforge/postgresql/studio/query-profiler.html dbForge Studio for PostgreSQL] helps to identify productivity bottlenecks, and provides PostgreSQL performance tuning.<br />
* The [https://github.com/jfcoz/postgresqltuner postgresqltuner.pl] script can analyze the configuration and make tuning recommendations. <br />
* [https://pgbadger.darold.net/ PgBadger] analyse PostgreSQL logs to generate performance reports.<br />
* [https://www.pgmustard.com/ pgMustard] provides tuning advice based on EXPLAIN ANALYZE output.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-LISTEN-ADDRESSES listen_addresses] ==<br />
<br />
By default, PostgreSQL only responds to connections from the local host. If you want your server to be accessible from other systems via standard TCP/IP networking, you need to change listen_addresses from its default. The usual approach is to set it to listen to all addresses like this:<br />
<br />
<code><pre><br />
listen_addresses = '*'<br />
</pre></code><br />
<br />
And then control who can and cannot connect via the [http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html pg_hba.conf] file.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-MAX-CONNECTIONS max_connections]==<br />
<br />
max_connections sets exactly that: the maximum number of client connections allowed. This is very important to some of the below parameters (particularly work_mem) because there are some memory resources that are or can be allocated on a per-client basis, so the maximum number of clients suggests the maximum possible memory use. Generally, PostgreSQL on good hardware can support a few hundred connections. If you want to have thousands instead, you should consider using [[Replication, Clustering, and Connection Pooling|connection pooling software]] to reduce the connection overhead.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-SHARED-BUFFERS shared_buffers]==<br />
<br />
The shared_buffers configuration parameter determines how much memory is dedicated to PostgreSQL to use for caching data. One reason the defaults are low is because on some platforms (like older Solaris versions and SGI), having large values requires invasive action like recompiling the kernel. Even on a modern Linux system, the stock kernel will likely not allow setting shared_buffers to over 32MB without adjusting kernel settings first. (PostgreSQL 9.4 and later use a different shared memory mechanism, so kernel settings will usually not have to be adjusted there.)<br />
<br />
If you have a system with 1GB or more of RAM, a reasonable starting value for shared_buffers is 1/4 of the memory in your system. If you have less RAM you'll have to account more carefully for how much RAM the OS is taking up; closer to 15% is more typical there. There are some workloads where even larger settings for shared_buffers are effective, but given the way PostgreSQL also relies on the operating system cache, it's unlikely you'll find using more than 40% of RAM to work better than a smaller amount.<br />
<br />
Be aware that if your system or PostgreSQL build is 32-bit, it might not be practical to set shared_buffers above 2 ~ 2.5GB. See [http://rhaas.blogspot.jp/2011/05/sharedbuffers-on-32-bit-systems.html this blog post] for details.<br />
<br />
Changing this setting requires restarting the database. Also, this is a hard allocation of memory; the whole thing gets allocated out of virtual memory when the database starts.<br />
<br />
;PostgreSQL 9.2 or earlier<br />
<br />
If you are running PostgreSQL 9.2 or earlier, it's likely that in order to increase the value of shared_buffers you will have to increase the amount of memory your operating system allows you to allocate to a single shared memory segment. On UNIX-like systems, if you set it above what's supported, you'll get a message like this:<br />
<br />
<code><pre><br />
IpcMemoryCreate: shmget(key=5432001, size=415776768, 03600) failed: Invalid argument <br />
<br />
This error usually means that PostgreSQL's request for a shared memory <br />
segment exceeded your kernel's SHMMAX parameter. You can either <br />
reduce the request size or reconfigure the kernel with larger SHMMAX. <br />
To reduce the request size (currently 415776768 bytes), reduce <br />
PostgreSQL's shared_buffers parameter (currently 50000) and/or <br />
its max_connections parameter (currently 12).<br />
</pre></code><br />
<br />
See [http://www.postgresql.org/docs/current/static/kernel-resources.html Managing Kernel Resources] for details on how to correct this.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-EFFECTIVE-CACHE-SIZE effective_cache_size]==<br />
<br />
effective_cache_size should be set to an estimate of how much memory is available for disk caching by the operating system and within the database itself, after taking into account what's used by the OS itself and other applications. This is a guideline for how much memory you expect to be available in the OS and PostgreSQL buffer caches, not an allocation! This value is used only by the PostgreSQL query planner to figure out whether plans it's considering would be expected to fit in RAM or not. If it's set too low, indexes may not be used for executing queries the way you'd expect. The setting for shared_buffers is not taken into account here--only the effective_cache_size value is, so it should include memory dedicated to the database too.<br />
<br />
Setting effective_cache_size to 1/2 of total memory would be a normal conservative setting, and 3/4 of memory is a more aggressive but still reasonable amount. You might find a better estimate by looking at your operating system's statistics. On UNIX-like systems, add the free+cached numbers from free or top to get an estimate. On Windows see the "System Cache" size in the Windows Task Manager's Performance tab. Changing this setting does not require restarting the database (HUP is enough).<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-wal.html#RUNTIME-CONFIG-WAL-CHECKPOINTS checkpoint_segments checkpoint_completion_target]==<br />
<br />
'''Note''': This applies to PostgreSQL 9.4 and below. [https://www.postgresql.org/docs/9.5/release-9-5.html PostgreSQL 9.5 introduced min_wal_size and max_wal_size] configuration parameters and removed checkpoint_segments. Please review the release notes and the documentation on [https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MIN-WAL-SIZE min_wal_size], [https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-MAX-WAL-SIZE max_wal_size] and [https://www.postgresql.org/docs/current/wal-configuration.html WAL configuration].<br />
<br />
PostgreSQL writes new transactions to the database in files called WAL segments that are 16MB in size. Every time checkpoint_segments worth of these files have been written, by default 3, a checkpoint occurs. Checkpoints can be resource intensive, and on a modern system doing one every 48MB will be a serious performance bottleneck. Setting checkpoint_segments to a much larger value improves that. Unless you're running on a very small configuration, you'll almost certainly be better setting this to at least 10, which also allows usefully increasing the completion target.<br />
<br />
For more write-heavy systems, values from 32 (checkpoint every 512MB) to 256 (every 4GB) are popular nowadays. Very large settings use a lot more disk and will cause your database to take longer to recover, so make sure you're comfortable with both those things before large increases. Normally the large settings (>64/1GB) are only used for bulk loading. Note that whatever you choose for the segments, you'll still get a checkpoint at least every 5 minutes unless you also increase checkpoint_timeout (which isn't necessary on most systems).<br />
<br />
Checkpoint writes are spread out a bit while the system starts working toward the next checkpoint. You can spread those writes out further, lowering the average write overhead, by increasing the checkpoint_completion_target parameter to its useful maximum of 0.9 (aim to finish by the time 90% of the next checkpoint is here) rather than the default of 0.5 (aim to finish when the next one is 50% done). A setting of 0 gives something similar to the behavior of obsolete versions. The main reason the default isn't just 0.9 is that you need a larger checkpoint_segments value than the default for broader spreading to work well. For lots more information on checkpoint tuning, see [http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm Checkpoints and the Background Writer] (where you'll also learn why tuning the background writer parameters is challenging to do usefully).<br />
<br />
==[http://www.postgresql.org/docs/current/static/routine-vacuuming.html#AUTOVACUUM autovacuum]==<br />
<br />
The autovacuum process takes care of several maintenance chores inside your database that you really need. Generally, if you think you need to turn regular vacuuming off because it's taking too much time or resources, that means you're doing it wrong. The answer to almost all vacuuming problems is to vacuum more often, not less, so that each individual vacuum operation has less to clean up.<br />
<br />
However, it's acceptable to disable autovacuum for short periods of time, for instance when bulk loading large amounts of data.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-logging.html Logging]==<br />
<br />
There are many things you can log that may or may not be important to you. You should investigate the documentation on all of the options, but here are some tips & tricks to get you started:<br />
<br />
*log_destination & log_directory (& log_filename): What you set these options to is not as important as knowing they can give you hints to determine where your database server is logging to. Best practice would be to try and make this as similar as possible across your servers. Note that in some cases, the init script starting your database may be customizing the log destination in the command line used to start the database, overriding what's in the configuration files (and making it so you'll get different behavior if you run pg_ctl manually instead of using the init script).<br />
<br />
*log_min_error_statement: You should probably make sure this is at least on error, so that you will see any SQL commands which cause an error. should be the default on recent versions. <br />
<br />
*log_min_duration_statement: Not necessary for everyday use, but this can generate [[Logging Difficult Queries|logs of "slow queries"]] on your system. <br />
<br />
*log_line_prefix: Appends information to the start of each line. A good generic recommendation is '%t:%r:%u@%d:[%p]: ' : %t=timestamp, %u=db user name, %r=host connecting from, %d=database connecting to, %p=PID of connection. It may not be obvious what the PID is useful at first, but it can be vital for trying to troubleshoot problems in the future so better to put in the logs from the start.<br />
<br />
*log_statement: Choices of none, ddl, mod, all. Using all or mod in production would introduce overhead of the logging. The performance penalties for "all" would be significant if the workload is select intensive and less significant for write-intensive workloads. Turning the synchronous_commit to off would cause a more severe performance regression. DDL can sometime be helpful to discover rogue changes made outside of your recommend processes, by "cowboy DBAs" for example.<br />
<br />
There are also external tools such [https://pgbadger.darold.net/ pgbadger] that can analyze Postgres logs, see [[Monitoring]] for a comprehensive list.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-DEFAULT-STATISTICS-TARGET default_statistics_target]==<br />
<br />
The database software collects statistics about each of the tables in your database to decide how to execute queries against it. If you're not getting good execution query plans particularly on larger (or more varied) tables you should increase default_statistics_target then ANALYZE the database again (or wait for autovacuum to do it for you). <br />
<br />
Increasing the default_statistics_target may be useful but the default value shipped with PostgreSQL is a reasonable starting point.<br />
<br />
;PostgreSQL 8.3 and earlier<br />
<br />
In PostgreSQL 8.3 and earlier increasing the supplied default_statistics_target would often greatly improve query plans. The starting default_statistics_target value was raised from 10 to 100 in PostgreSQL 8.4. The maximum value for the parameter was also increased from 1000 to 10,000 in 8.4.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM work_mem]==<br />
<br />
If you do a lot of complex sorts, and have a lot of memory, then increasing the <code>work_mem</code> parameter allows PostgreSQL to do larger in-memory sorts which, unsurprisingly, will be faster than disk-based equivalents.<br />
<br />
This size is applied to each and every sort done by each user, and complex queries can use multiple working memory sort buffers. Set it to 50MB, and have 30 users submitting queries, and you are soon using 1.5GB of real memory. Furthermore, if a query involves doing merge sorts of 8 tables, that requires 8 times work_mem. You need to consider what you set max_connections to in order to size this parameter correctly. This is a setting where data warehouse systems, where users are submitting very large queries, can readily make use of many gigabytes of memory.<br />
<br />
[http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#GUC-LOG-TEMP-FILES log_temp_files] can be used to log sorts, hashes, and temp files which can be useful in figuring out if sorts are spilling to disk instead of fitting in memory. You can see sorts spilling to disk using <code>EXPLAIN ANALYZE</code> plans as well. For example, if you see a line like <code>Sort Method: external merge Disk: 7526kB</code> in the output of EXPLAIN ANALYZE, a <code>work_mem</code> of at least 8MB would keep the intermediate data in memory and likely improve the query response time (although it may take substantially more than 8MB to do the sort entirely in memory, as data on disk is stored in a more compact format).<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM maintenance_work_mem]==<br />
<br />
Specifies the maximum amount of memory to be used by maintenance operations, such as VACUUM, CREATE INDEX, and ALTER TABLE ADD FOREIGN KEY. It defaults to 64 megabytes (64MB) since version 9.4. Since only one of these operations can be executed at a time by a database session, and an installation normally doesn't have many of them running concurrently, it's safe to set this value significantly larger than work_mem. Larger settings might improve performance for vacuuming and for restoring database dumps.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-WAL-SYNC-METHOD wal_sync_method wal_buffers]==<br />
<br />
After every transaction, PostgreSQL forces a commit to disk out to its write-ahead log. This can be done a couple of ways, and on some platforms other options than the shipped wal_sync_method are considerably faster than the conservative default. open_sync is the most common non-default setting switched to, on platforms that support it but default to one of the fsync methods. See [http://www.westnet.com/~gsmith/content/postgresql/TuningPGWAL.htm Tuning PostgreSQL WAL Synchronization] for a lot of background on this topic. Note that open_sync writing is buggy on some platforms (such as [http://lwn.net/Articles/350219/ Linux]), and you should (as always) do plenty of tests under a heavy write load to make sure that you haven't made your system less stable with this change. [[Reliable Writes]] contains more information on this topic.<br />
<br />
wal_buffers defaults to 1/32 of the size of shared_buffers, with an upper limit of 16MB (reached when shared_buffers=512MB). Adjustments to the default are required much less often than in earlier PostgreSQL releases.<br />
<br />
;PostgreSQL 9.0 and earlier<br />
<br />
Linux kernels starting with version 2.6.33 cause PostgreSQL versions before 9.0.2 to default to wal_sync_method=open_datasync; before kernel 2.6.32 the default picked was always fdatasync. This can cause a significant performance decrease when combined with small writes and/or small values for wal_buffers. PostgreSQL versions starting with 9.0.2 again default wal_sync_method to fdatasync when running on Linux.<br />
<br />
On PostgreSQL 9.0 and earlier, increasing wal_buffers from its tiny default of a small number of kilobytes is helpful for write-heavy systems. Benchmarking generally suggests that just increasing to 1MB is enough for some large systems, and given the amount of RAM in modern servers allocating a full WAL segment (16MB, the useful upper-limit here) is reasonable. <br />
<br />
Changing wal_buffers requires a database restart.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-CONSTRAINT-EXCLUSION constraint_exclusion]==<br />
<br />
<tt>constraint_exclusion</tt> now defaults to a new choice: <tt>partition</tt>. This will only enable constraint exclusion for partitioned tables which is the right thing to do in nearly all cases.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAX-PREPARED-TRANSACTIONS max_prepared_transactions]==<br />
<br />
This setting is used for managing 2 phase commit. If you do not use two phase commit (and if you don't know what it is, you don't use it), then you can set this value to 0. That will save a little bit of shared memory. For database systems with a large number (at least hundreds) of concurrent connections, be aware that this setting also affects the number of available lock-slots in pg_locks, so you may want to leave it at the default setting. There is a formula for how much memory gets allocated [http://www.postgresql.org/docs/current/static/kernel-resources.html#SHARED-MEMORY-PARAMETERS in the docs] and in the default postgresql.conf.<br />
<br />
Changing max_prepared_transactions requires a server restart.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT synchronous_commit]==<br />
PostgreSQL can only safely use a write cache if it has a battery backup. See [http://www.postgresql.org/docs/current/static/wal-reliability.html WAL reliability] for an essential introduction to this topic. No, really; go read that right now, it's vital to understand that if you want your database to work right.<br />
<br />
You may be limited to approximately 100 transaction commits per second per client in situations where you don't have such a durable write cache (and perhaps only 500/second even with lots of clients).<br />
<br />
For situations where a small amount of data loss is acceptable in return for a large boost in how many updates you can do to the database per second, consider switching synchronous commit off. This is particularly useful in the situation where you do not have a battery-backed write cache on your disk controller, because you could potentially get thousands of commits per second instead of just a few hundred.<br />
<br />
For obsolete versions of PostgreSQL, you may find people recommending that you set ''fsync=off'' to speed up writes on busy systems. This is dangerous--a power loss could result in your database getting corrupted and not able to start again. Synchronous commit doesn't introduce the risk of ''corruption'', which is really bad, just some risk of data ''loss''.<br />
<br />
==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-RANDOM-PAGE-COST random_page_cost]==<br />
This setting suggests to the optimizer how long it will take your disks to seek to a random disk page, as a multiple of how long a sequential read (with a cost of 1.0) takes. If you have particularly fast disks, as commonly found with RAID arrays of SCSI disks, it may be appropriate to lower random_page_cost, which will encourage the query optimizer to use random access index scans. Some feel that 4.0 is always too large on current hardware; it's not unusual for administrators to standardize on always setting this between 2.0 and 3.0 instead. In some cases that behavior is a holdover from earlier PostgreSQL versions where having random_page_cost too high was more likely to screw up plan optimization than it is now (and setting at or below 2.0 was regularly necessary). Since these cost estimates are just that--estimates--it shouldn't hurt to try lower values.<br />
<br />
But this not where you should start to search for plan problems. Note that random_page_cost is pretty far down this list (at the end in fact). If you are getting bad plans, this shouldn't be the first thing you look at, even though lowering this value may be effective. Instead, you should start by making sure autovacuum is working properly, that you are collecting enough statistics, and that you have correctly sized the memory parameters for your server--all the things gone over above. After you've done all those much more important things, if you're still getting bad plans ''then'' you should see if lowering random_page_cost is still useful.<br />
<br />
[[Category:Administration]] [[Category:Performance]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35202PostgreSQL 13 Open Items2020-08-02T02:28:37Z<p>Davidrowley: Mark incremental sort's use of long datatype as fixed.</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20200724012248.y77rpqc73agrsvb3@development HashAggs-that-spill costing seems off in cases where we spill and work_mem is far below the "optimal" amount for the aggregate]<br />
** "despite writing about twice as much data, the hashagg cost is estimated to be much lower than the sort".<br />
** At the very low end, the amount of I/O performed by hash aggregate can significantly exceed what we see with the equivalent Group agg + sort.<br />
** Original commit: {{PgCommitURL|1f39bce0}}<br />
** Owner: Jeff Davis<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn5PCBLUrrds=hD439LtWP+PD7ekRTd=8LdtqJ+KO5D1Q@mail.gmail.com HashAggs-that-spill preallocation subtly broke trace_sort and EXPLAIN ANALYZE "%u disk blocks used" statistics]<br />
** We should account for "preallocated" though unused blocks, which currently get included in the instrumentation.<br />
** Original commit: {{PgCommitURL|896ddf9b}}<br />
** Owner: Jeff Davis<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table]<br />
** Affects v12 and probably v11 (partition pruning)<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
** Fixed at: {{PgCommitURL|a44dd932ff3816de7fe0414063cfcc5656117c3a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAB%3DJe-GOWMj1PTPkeUhjqQp-4W3%3DnW-pXe2Hjax6rJFffB5_Aw%40mail.gmail.com Initiating Physical Replication on a Logical Replication Session]<br />
<br />
* [https://www.postgresql.org/message-id/20200415233848.saqp72pcjv2y6ryi%40alap3.anarazel.de xid wraparound danger due to INDEX_CLEANUP false.]<br />
** Affects v12+<br />
** This bug [https://www.postgresql.org/message-id/CA+TgmoYD7Xpr1DWEWWXxiw4-WC1NBJf3Rb9D2QGpVYH9ejz9fA@mail.gmail.com will not be fixed] in v13 or other backbranches.<br />
** Maybe it can be fixed by future work that makes B-Tree page recycling work at the tail end of the same VACUUM operation that initially deletes the pages, but that's out of scope for now.<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAAaqYe97a3xf=5Q0ZjPcQQGX-rAPL9CNFkfupqzCt7g4TrVLrA@mail.gmail.com EXPLAIN ANALYZE's non-text output should consistently include all fields for incremental sort, meaning fields "not applicable" to text format output should be shown as 0]<br />
** [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com Nothing to do for incremental sort], which at least manages to show EXPLAIN ANALYZE output that's consistent with regular sort nodes.<br />
** Original commit: {{PgCommitURL|d2d8a229}}<br />
<br />
* [https://www.postgresql.org/message-id/20200625203629.7m6yvut7eqblgmfo@alap3.anarazel.de Many users rely on hashagg exceeding work_mem, regardless of whether or not that is the intended behavior in Postgres 12]<br />
** When these users don't continue to get fast in-memory hash aggs after an upgrade to Postgres 13, they'll simply conclude that it's a regression.<br />
** Increasing work_mem isn't usually an option, since that affects everything equally.<br />
** We decided to ameliorate problem using the new hash_mem_multiplier GUC, which allows users to preferentially give hash-based executor nodes more memory.<br />
** Hopefully it won't also prove necessary to add an escape hatch. In any case this isn't the final word.<br />
** Owner: Peter Geoghegan<br />
** Fixed at: {{PgCommitURL|d6c08e29e7bc8bc3bf49764192c4a9c71fc0b097}}<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for hashagg_avoid_disk_plan GUC]<br />
** hashagg_avoid_disk_plan GUC preserves the plan time behavior from Postgres 12, but not the execution time behavior.<br />
** We decided to remove the GUC altogether.<br />
** Owner: Peter Geoghegan<br />
** Fixed at: {{PgCommitURL|bcbf9446a2983b6452c19cc50050456be262f7c5}}<br />
<br />
* [https://www.postgresql.org/message-id/20200612213715.op4ye4q7gktqvpuo%40alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: LookupTupleHashEntryHash() pipeline stall]<br />
** Original commit: {{PgCommitURL|1f39bce0}}<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|200f6100a9f9fc71273aeb6aceac4430f3437195}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/2edc7b27-031f-b2b6-0db2-864241c91cb9%402ndquadrant.com Output columns shown by new \dAo and \dAp psql commands are arguably confusing, inconsistent]<br />
** Original commit: {{PgCommitURL|b0b5e20cd8d}}<br />
** Owner: Alexander Korotkov<br />
** Fixed at: {{PgCommitURL|8d2ed66e4107ef27d05aef682c68af5952af7690}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: "unnecessary" attributes were removed before spilling, which is pretty much wasted effort when we don't spill]<br />
** Original commit: {{PgCommitURL|1f39bce0}} <br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|2302302236a0c7aeba3377d78dd9d80ba53247df}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2Bfd4k5_pPAYRTDrO2PbtTOe0eHQpBvuqmCr8ic39uTNmR49Eg%40mail.gmail.com Replication slot spill statistics in the wrong place]<br />
** Original commit: {{PgCommitURL|9290ad198b1}}<br />
** Owner: Tomas Vondra, Amit Kapila<br />
** Feature has been reverted<br />
** Fixed/reverted at: {{PgCommitURL|d973747281caece520236e93d255c654cc613ec9}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com EXPLAIN ANALYZE's non-text output should consistently include all fields for hash aggregate, meaning fields "not applicable" to text format output should be shown as 0]<br />
** Owner: David Rowley<br />
** Fixed at: {{PgCommitURL|40efbf8706cdd96e06bc4d1754272e46d9857875}}<br />
<br />
* [https://www.postgresql.org/message-id/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com min_safe_lsn column in pg_replication_slots view]<br />
** Fixed at: {{PgCommitURL|c54b5891f415df36809de1aeb97e4574d5456d69}}<br />
<br />
* [https://www.postgresql.org/message-id/2895b53b033c47ccb22972b589050dd9@EX13D05UWC001.ant.amazon.com pg_stat_statements + track_planning performance regression]<br />
** Fixed at: {{PgCommitURL|d1763ea8c9c32837d373a196ed0c2e1256a55824}}<br />
** Owner: Fujii Masao<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
** The deduplication feature will [https://www.postgresql.org/message-id/CAH2-Wzm1u8HmCamGj2LmtvUudzai5qDJryTotu++JLLD9KVMRw@mail.gmail.com remain enabled by default].<br />
<br />
* [https://www.postgresql.org/message-id/flat/a9408304-4381-a5af-d259-e55d349ae4ce@2ndquadrant.com rethink libpq's default min SSL version]<br />
** Commit: {{PgCommitURL|6e682f61a5bdb08164a805419144318db6b7229f}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/8d55969f-ba37-b89a-6494-e9322ccdb35d%40oss.nttdata.com Review for GetWALAvailability()]<br />
** Commit: {{PgCommitURL|b8fd4e02c6d01183bf6def5897ad6cf7766bfff4}}<br />
<br />
* [https://www.postgresql.org/message-id/f91de4fb-a7ab-b90e-8132-74796e049d51%40oss.nttdata.com Assertion failure in pg_copy_logical_replication_slot()]<br />
** Commit: {{PgCommitURL|a82ba066ea217e7fe4da3c20ced01e7ca976a351}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040624.GA17995@telsasoft.com hashagg spill to disk] Owner: Jeff Davis<br />
** Commit: {{PgCommitURL|d73e9a57bf5bd977d9bf36bc07c77a1acf45e35b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200717153540.GA17100@alvherre.pgsql Should pg_stat_activity.leader_pid be NULL for leaders themselves?]<br />
** Commit: {{PgCommitURL|11a68e4b53ffccf336a2faf5fa380acda28e880b}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvqTvD3bXBiC5cmuoATFYeP%2BRSkv5WTgfyuBb6JpwKmSoQ%40mail.gmail.com EXPLAIN ANALYZE output for HashAgg could be better aligned to Hash Join's output]<br />
** Commit: {{PgCommitURL|a57c837e5cdf601d6ec05e5e10a40d01f1d2b84e}}<br />
<br />
* [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]<br />
** Commit: {{PgCommitURL|22c105595fc736ae94ce3b806da16b0bd8e94fb8}}<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Commit: {{PgCommitURL|fd49d53807575e009f7b66771d48c9356344d7d1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Commit: {{PgCommitURL|9bdb300dedf086cc54edf740088208e6b24307ef}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: June 25, 2020<br />
* Beta 3: August 13, 2020<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35178PostgreSQL 13 Open Items2020-07-31T02:11:05Z<p>Davidrowley: /* Open Issues */ Add open item about use of long data type in incremental sort code.</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20200724012248.y77rpqc73agrsvb3@development HashAggs-that-spill costing seems off in cases where we spill and work_mem is far below the "optimal" amount for the aggregate]<br />
** "despite writing about twice as much data, the hashagg cost is estimated to be much lower than the sort".<br />
** At the very low end, the amount of I/O performed by hash aggregate can significantly exceed what we see with the equivalent Group agg + sort.<br />
** Original commit: {{PgCommitURL|1f39bce0}}<br />
** Owner: Jeff Davis<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn5PCBLUrrds=hD439LtWP+PD7ekRTd=8LdtqJ+KO5D1Q@mail.gmail.com HashAggs-that-spill preallocation subtly broke trace_sort and EXPLAIN ANALYZE "%u disk blocks used" statistics]<br />
** We should account for "preallocated" though unused blocks, which currently get included in the instrumentation.<br />
** Original commit: {{PgCommitURL|896ddf9b}}<br />
** Owner: Jeff Davis<br />
<br />
* [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]<br />
** Owner: James Coleman, Tomas Vondra<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table]<br />
** Affects v12 and probably v11 (partition pruning)<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
** Fixed at: {{PgCommitURL|a44dd932ff3816de7fe0414063cfcc5656117c3a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAB%3DJe-GOWMj1PTPkeUhjqQp-4W3%3DnW-pXe2Hjax6rJFffB5_Aw%40mail.gmail.com Initiating Physical Replication on a Logical Replication Session]<br />
<br />
* [https://www.postgresql.org/message-id/20200415233848.saqp72pcjv2y6ryi%40alap3.anarazel.de xid wraparound danger due to INDEX_CLEANUP false.]<br />
** Affects v12+<br />
** This bug [https://www.postgresql.org/message-id/CA+TgmoYD7Xpr1DWEWWXxiw4-WC1NBJf3Rb9D2QGpVYH9ejz9fA@mail.gmail.com will not be fixed] in v13 or other backbranches.<br />
** Maybe it can be fixed by future work that makes B-Tree page recycling work at the tail end of the same VACUUM operation that initially deletes the pages, but that's out of scope for now.<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAAaqYe97a3xf=5Q0ZjPcQQGX-rAPL9CNFkfupqzCt7g4TrVLrA@mail.gmail.com EXPLAIN ANALYZE's non-text output should consistently include all fields for incremental sort, meaning fields "not applicable" to text format output should be shown as 0]<br />
** [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com Nothing to do for incremental sort], which at least manages to show EXPLAIN ANALYZE output that's consistent with regular sort nodes.<br />
** Original commit: {{PgCommitURL|d2d8a229}}<br />
<br />
* [https://www.postgresql.org/message-id/20200625203629.7m6yvut7eqblgmfo@alap3.anarazel.de Many users rely on hashagg exceeding work_mem, regardless of whether or not that is the intended behavior in Postgres 12]<br />
** When these users don't continue to get fast in-memory hash aggs after an upgrade to Postgres 13, they'll simply conclude that it's a regression.<br />
** Increasing work_mem isn't usually an option, since that affects everything equally.<br />
** We decided to ameliorate problem using the new hash_mem_multiplier GUC, which allows users to preferentially give hash-based executor nodes more memory.<br />
** Hopefully it won't also prove necessary to add an escape hatch. In any case this isn't the final word.<br />
** Owner: Peter Geoghegan<br />
** Fixed at: {{PgCommitURL|d6c08e29e7bc8bc3bf49764192c4a9c71fc0b097}}<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for hashagg_avoid_disk_plan GUC]<br />
** hashagg_avoid_disk_plan GUC preserves the plan time behavior from Postgres 12, but not the execution time behavior.<br />
** We decided to remove the GUC altogether.<br />
** Owner: Peter Geoghegan<br />
** Fixed at: {{PgCommitURL|bcbf9446a2983b6452c19cc50050456be262f7c5}}<br />
<br />
* [https://www.postgresql.org/message-id/20200612213715.op4ye4q7gktqvpuo%40alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: LookupTupleHashEntryHash() pipeline stall]<br />
** Original commit: {{PgCommitURL|1f39bce0}}<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|200f6100a9f9fc71273aeb6aceac4430f3437195}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/2edc7b27-031f-b2b6-0db2-864241c91cb9%402ndquadrant.com Output columns shown by new \dAo and \dAp psql commands are arguably confusing, inconsistent]<br />
** Original commit: {{PgCommitURL|b0b5e20cd8d}}<br />
** Owner: Alexander Korotkov<br />
** Fixed at: {{PgCommitURL|8d2ed66e4107ef27d05aef682c68af5952af7690}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: "unnecessary" attributes were removed before spilling, which is pretty much wasted effort when we don't spill]<br />
** Original commit: {{PgCommitURL|1f39bce0}} <br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|2302302236a0c7aeba3377d78dd9d80ba53247df}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2Bfd4k5_pPAYRTDrO2PbtTOe0eHQpBvuqmCr8ic39uTNmR49Eg%40mail.gmail.com Replication slot spill statistics in the wrong place]<br />
** Original commit: {{PgCommitURL|9290ad198b1}}<br />
** Owner: Tomas Vondra, Amit Kapila<br />
** Feature has been reverted<br />
** Fixed/reverted at: {{PgCommitURL|d973747281caece520236e93d255c654cc613ec9}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com EXPLAIN ANALYZE's non-text output should consistently include all fields for hash aggregate, meaning fields "not applicable" to text format output should be shown as 0]<br />
** Owner: David Rowley<br />
** Fixed at: {{PgCommitURL|40efbf8706cdd96e06bc4d1754272e46d9857875}}<br />
<br />
* [https://www.postgresql.org/message-id/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com min_safe_lsn column in pg_replication_slots view]<br />
** Fixed at: {{PgCommitURL|c54b5891f415df36809de1aeb97e4574d5456d69}}<br />
<br />
* [https://www.postgresql.org/message-id/2895b53b033c47ccb22972b589050dd9@EX13D05UWC001.ant.amazon.com pg_stat_statements + track_planning performance regression]<br />
** Fixed at: {{PgCommitURL|d1763ea8c9c32837d373a196ed0c2e1256a55824}}<br />
** Owner: Fujii Masao<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
** The deduplication feature will [https://www.postgresql.org/message-id/CAH2-Wzm1u8HmCamGj2LmtvUudzai5qDJryTotu++JLLD9KVMRw@mail.gmail.com remain enabled by default].<br />
<br />
* [https://www.postgresql.org/message-id/flat/a9408304-4381-a5af-d259-e55d349ae4ce@2ndquadrant.com rethink libpq's default min SSL version]<br />
** Commit: {{PgCommitURL|6e682f61a5bdb08164a805419144318db6b7229f}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/8d55969f-ba37-b89a-6494-e9322ccdb35d%40oss.nttdata.com Review for GetWALAvailability()]<br />
** Commit: {{PgCommitURL|b8fd4e02c6d01183bf6def5897ad6cf7766bfff4}}<br />
<br />
* [https://www.postgresql.org/message-id/f91de4fb-a7ab-b90e-8132-74796e049d51%40oss.nttdata.com Assertion failure in pg_copy_logical_replication_slot()]<br />
** Commit: {{PgCommitURL|a82ba066ea217e7fe4da3c20ced01e7ca976a351}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040624.GA17995@telsasoft.com hashagg spill to disk] Owner: Jeff Davis<br />
** Commit: {{PgCommitURL|d73e9a57bf5bd977d9bf36bc07c77a1acf45e35b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200717153540.GA17100@alvherre.pgsql Should pg_stat_activity.leader_pid be NULL for leaders themselves?]<br />
** Commit: {{PgCommitURL|11a68e4b53ffccf336a2faf5fa380acda28e880b}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvqTvD3bXBiC5cmuoATFYeP%2BRSkv5WTgfyuBb6JpwKmSoQ%40mail.gmail.com EXPLAIN ANALYZE output for HashAgg could be better aligned to Hash Join's output]<br />
** Commit: {{PgCommitURL|a57c837e5cdf601d6ec05e5e10a40d01f1d2b84e}}<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Commit: {{PgCommitURL|fd49d53807575e009f7b66771d48c9356344d7d1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Commit: {{PgCommitURL|9bdb300dedf086cc54edf740088208e6b24307ef}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: June 25, 2020<br />
* Beta 3: August 13, 2020<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35169PostgreSQL 13 Open Items2020-07-28T23:49:39Z<p>Davidrowley: Mark EXPLAIN ANALYZE output for HashAgg not being similar enough to Hash Join as complete.</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20200625203629.7m6yvut7eqblgmfo@alap3.anarazel.de Many users rely on hashagg exceeding work_mem, regardless of whether or not that is the intended behavior in Postgres 12]<br />
** When these users don't continue to get fast in-memory hash aggs after an upgrade to Postgres 13, they'll simply conclude that it's a regression.<br />
** Increasing work_mem isn't usually an option, since that affects everything equally.<br />
** There are good general reasons to preferentially give hash aggregate more memory than a sort used for a group aggregate, so these users will certainly have a point if this happens.<br />
** We have a pending [https://www.postgresql.org/message-id/CAH2-Wz=YP4UcJwCLx51W47o95fh2nCYdFLtamv7nUmRch9+mrg@mail.gmail.com hash_mem_multiplier patch] which ameliorates the risk in an indirect way.<br />
<br />
* [https://www.postgresql.org/message-id/20200724012248.y77rpqc73agrsvb3@development HashAggs-that-spill costing seems off in cases where we spill and work_mem is far below the "optimal" amount for the aggregate]<br />
** "despite writing about twice as much data, the hashagg cost is estimated to be much lower than the sort".<br />
** At the very low end, the amount of I/O performed by hash aggregate can significantly exceed what we see with the equivalent Group agg + sort.<br />
<br />
* [https://www.postgresql.org/message-id/20200619040358.GZ17995@telsasoft.com EXPLAIN ANALYZE's non-text output should consistently include all fields for incremental sort, meaning fields "not applicable" to text format output should be shown as 0]<br />
** We fixed more or less the same issue in hash agg already, but we still need to fix incremental sort.<br />
** Original commit: {{PgCommitURL|d2d8a229}}<br />
** Owner: James Coleman, Tomas Vondra<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200728151002.GE20393%40telsasoft.com ItemPointer values should never be equal]<br />
** Affects all stable branches<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table.]<br />
** Affects v12 and probably v11 (partition pruning)<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
** Fixed at: {{PgCommitURL|a44dd932ff3816de7fe0414063cfcc5656117c3a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAB%3DJe-GOWMj1PTPkeUhjqQp-4W3%3DnW-pXe2Hjax6rJFffB5_Aw%40mail.gmail.com Initiating Physical Replication on a Logical Replication Session]<br />
<br />
* [https://www.postgresql.org/message-id/20200415233848.saqp72pcjv2y6ryi%40alap3.anarazel.de xid wraparound danger due to INDEX_CLEANUP false.]<br />
** Affects v12<br />
** This bug [https://www.postgresql.org/message-id/CA+TgmoYD7Xpr1DWEWWXxiw4-WC1NBJf3Rb9D2QGpVYH9ejz9fA@mail.gmail.com will not be fixed] in v13 or other backbranches.<br />
** Maybe it can be fixed by future work that makes B-Tree page recycling work at the tail end of the same VACUUM operation that initially deletes the pages, but that's out of scope for now.<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta3 ===<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for hashagg_avoid_disk_plan GUC]<br />
** hashagg_avoid_disk_plan GUC preserves the plan time behavior from Postgres 12, but not the execution time behavior.<br />
** We decided to remove the GUC altogether.<br />
** Owner: Peter Geoghegan<br />
** Fixed at: {{PgCommitURL|bcbf9446a2983b6452c19cc50050456be262f7c5}}<br />
<br />
* [https://www.postgresql.org/message-id/20200612213715.op4ye4q7gktqvpuo%40alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: LookupTupleHashEntryHash() pipeline stall]<br />
** Original commit: {{PgCommitURL|1f39bce0}}<br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|200f6100a9f9fc71273aeb6aceac4430f3437195}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/2edc7b27-031f-b2b6-0db2-864241c91cb9%402ndquadrant.com Output columns shown by new \dAo and \dAp psql commands are arguably confusing, inconsistent]<br />
** Original commit: {{PgCommitURL|b0b5e20cd8d}}<br />
** Owner: Alexander Korotkov<br />
** Fixed at: {{PgCommitURL|8d2ed66e4107ef27d05aef682c68af5952af7690}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: "unnecessary" attributes were removed before spilling, which is pretty much wasted effort when we don't spill]<br />
** Original commit: {{PgCommitURL|1f39bce0}} <br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|2302302236a0c7aeba3377d78dd9d80ba53247df}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2Bfd4k5_pPAYRTDrO2PbtTOe0eHQpBvuqmCr8ic39uTNmR49Eg%40mail.gmail.com Replication slot spill statistics in the wrong place]<br />
** Original commit: {{PgCommitURL|9290ad198b1}}<br />
** Owner: Tomas Vondra, Amit Kapila<br />
** Feature has been reverted<br />
** Fixed/reverted at: {{PgCommitURL|d973747281caece520236e93d255c654cc613ec9}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com EXPLAIN ANALYZE's non-text output should consistently include all fields for hash aggregate, meaning fields "not applicable" to text format output should be shown as 0]<br />
** Owner: David Rowley<br />
** Fixed at: {{PgCommitURL|40efbf8706cdd96e06bc4d1754272e46d9857875}}<br />
<br />
* [https://www.postgresql.org/message-id/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com min_safe_lsn column in pg_replication_slots view]<br />
** Fixed at: {{PgCommitURL|c54b5891f415df36809de1aeb97e4574d5456d69}}<br />
<br />
* [https://www.postgresql.org/message-id/2895b53b033c47ccb22972b589050dd9@EX13D05UWC001.ant.amazon.com pg_stat_statements + track_planning performance regression]<br />
** Fixed at: {{PgCommitURL|d1763ea8c9c32837d373a196ed0c2e1256a55824}}<br />
** Owner: Fujii Masao<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
** The deduplication feature will [https://www.postgresql.org/message-id/CAH2-Wzm1u8HmCamGj2LmtvUudzai5qDJryTotu++JLLD9KVMRw@mail.gmail.com remain enabled by default].<br />
<br />
* [https://www.postgresql.org/message-id/flat/a9408304-4381-a5af-d259-e55d349ae4ce@2ndquadrant.com rethink libpq's default min SSL version]<br />
** Commit: {{PgCommitURL|6e682f61a5bdb08164a805419144318db6b7229f}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/8d55969f-ba37-b89a-6494-e9322ccdb35d%40oss.nttdata.com Review for GetWALAvailability()]<br />
** Commit: {{PgCommitURL|b8fd4e02c6d01183bf6def5897ad6cf7766bfff4}}<br />
<br />
* [https://www.postgresql.org/message-id/f91de4fb-a7ab-b90e-8132-74796e049d51%40oss.nttdata.com Assertion failure in pg_copy_logical_replication_slot()]<br />
** Commit: {{PgCommitURL|a82ba066ea217e7fe4da3c20ced01e7ca976a351}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040624.GA17995@telsasoft.com hashagg spill to disk] Owner: Jeff Davis<br />
** Commit: {{PgCommitURL|d73e9a57bf5bd977d9bf36bc07c77a1acf45e35b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200717153540.GA17100@alvherre.pgsql Should pg_stat_activity.leader_pid be NULL for leaders themselves?]<br />
** Commit: {{PgCommitURL|11a68e4b53ffccf336a2faf5fa380acda28e880b}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvqTvD3bXBiC5cmuoATFYeP%2BRSkv5WTgfyuBb6JpwKmSoQ%40mail.gmail.com EXPLAIN ANALYZE output for HashAgg could be better aligned to Hash Join's output]<br />
** Commit: {{PgCommitURL|a57c837e5cdf601d6ec05e5e10a40d01f1d2b84e}}<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Commit: {{PgCommitURL|fd49d53807575e009f7b66771d48c9356344d7d1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Commit: {{PgCommitURL|9bdb300dedf086cc54edf740088208e6b24307ef}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: June 25, 2020<br />
* Beta 3: August 13, 2020<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35160PostgreSQL 13 Open Items2020-07-26T23:01:03Z<p>Davidrowley: /* Open Issues */ Added item about unnecessary variations between Hash Agg and Hash Join EXPLAIN ANALYZE output</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list (within its applicable open item category).<br />
<br />
=== Hash Aggs that spill (commit 1f39bce0) issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200625203629.7m6yvut7eqblgmfo@alap3.anarazel.de Many users rely on hashagg exceeding work_mem, regardless of whether or not that is the intended behavior in Postgres 12]<br />
** When these users don't continue to get fast in-memory hash aggs after an upgrade to Postgres 13, they'll simply conclude that it's a regression.<br />
** Increasing work_mem isn't usually an option, since that affects everything equally.<br />
** There are good general reasons to preferentially give hash aggregate more memory than a sort used for a group aggregate, so these users will certainly have a point if this happens.<br />
** We have a pending [https://www.postgresql.org/message-id/CAH2-Wz=YP4UcJwCLx51W47o95fh2nCYdFLtamv7nUmRch9+mrg@mail.gmail.com hash_mem_multiplier patch] which proposes to solve this issue in an indirect way.<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for hashagg_avoid_disk_plan GUC] (the GUC formerly known as enable_hashagg_disk, renamed by {{PgCommitURL|92c58fd9}})<br />
** This thread is [https://postgr.es/m/CAH2-WzmD+i1pG6rc1+Cjc4V6EaFJ_qSuKCCHVnH=oruqD-zqow@mail.gmail.com now mostly a discussion] of the preceding "Many users rely on hashagg exceeding work_mem, regardless of whether or not that is the intended behavior in Postgres 12" item.<br />
** You can think of this hashagg_avoid_disk_plan item as being about providing users with a mechanism to avoid hash aggregation when planning, without reliably ensuring that it is avoided at execution time.<br />
** In other words, it preserves the plan time behavior from Postgres 12, but not the execution time behavior.<br />
** In theory there should be no difference (in theory these two open items are one and the same). In practice there is a huge difference, because group estimates are frequently off by orders of magnitude, and because hash aggs greatly benefit from more memory (unlike the equivalent group aggregate + sort plan).<br />
** We have a pending [https://www.postgresql.org/message-id/CAH2-Wz=YP4UcJwCLx51W47o95fh2nCYdFLtamv7nUmRch9+mrg@mail.gmail.com patch] that removes the hashagg_avoid_disk_plan GUC (which is part of a patch series that also adds the hash_mem_multiplier GUC).<br />
<br />
* [https://www.postgresql.org/message-id/20200612213715.op4ye4q7gktqvpuo%40alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: LookupTupleHashEntryHash() pipeline stall]<br />
** Note that {{PgCommitURL|4cad2534}} was reverted already (by {{PgCommitURL|0babd109}}, which anticipated {{PgCommitURL|23023022}}), but that alone isn't enough.<br />
** A patch that fixes the issue [https://www.postgresql.org/message-id/CAH2-Wzne5FQ31XaQz_-qJ_fTfc_NvwdTyT7BdqESvGnftmCsfw@mail.gmail.com is available].<br />
** This is [https://www.postgresql.org/message-id/20200724235114.xy4a2egntf7y7djh@alap3.anarazel.de still not fixed] in late July -- this presumably complicates resolving all the other hash agg open items, since we don't have a representative Postgres 13 baseline for in-memory hash agg performance.<br />
<br />
* [https://www.postgresql.org/message-id/20200724012248.y77rpqc73agrsvb3@development HashAggs-that-spill costing seems off in cases where we spill and work_mem is far below the "optimal" amount for the aggregate]<br />
** "despite writing about twice as much data, the hashagg cost is estimated to be much lower than the sort".<br />
** At the very low end, the amount of I/O performed by hash aggregate can significantly exceed what we see with the equivalent Group agg + sort.<br />
<br />
=== Other issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200619040358.GZ17995@telsasoft.com EXPLAIN ANALYZE's non-text output should consistently include all fields for incremental sort, meaning fields "not applicable" to text format output should be shown as 0]<br />
** We fixed more or less the same issue in hash agg already, but we still need to fix incremental sort.<br />
** Original commit: {{PgCommitURL|d2d8a229}}<br />
** Owner: James Coleman, Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvqTvD3bXBiC5cmuoATFYeP%2BRSkv5WTgfyuBb6JpwKmSoQ%40mail.gmail.com EXPLAIN ANALYZE output for HashAgg could be better aligned to Hash Join's output]<br />
** Owner: David Rowley<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table.]<br />
** Affects v12 and probably v11 (partition pruning)<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
** Fixed at: {{PgCommitURL|a44dd932ff3816de7fe0414063cfcc5656117c3a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAB%3DJe-GOWMj1PTPkeUhjqQp-4W3%3DnW-pXe2Hjax6rJFffB5_Aw%40mail.gmail.com Initiating Physical Replication on a Logical Replication Session]<br />
<br />
* [https://www.postgresql.org/message-id/20200415233848.saqp72pcjv2y6ryi%40alap3.anarazel.de xid wraparound danger due to INDEX_CLEANUP false.]<br />
** Affects v12<br />
** This bug [https://www.postgresql.org/message-id/CA+TgmoYD7Xpr1DWEWWXxiw4-WC1NBJf3Rb9D2QGpVYH9ejz9fA@mail.gmail.com will not be fixed] in v13 or other backbranches.<br />
** Maybe it can be fixed by future work that makes B-Tree page recycling work at the tail end of the same VACUUM operation that initially deletes the pages, but that's out of scope for now.<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/2edc7b27-031f-b2b6-0db2-864241c91cb9%402ndquadrant.com Output columns shown by new \dAo and \dAp psql commands are arguably confusing, inconsistent]<br />
** Original commit: {{PgCommitURL|b0b5e20cd8d}}<br />
** Owner: Alexander Korotkov<br />
** Fixed at: {{PgCommitURL|8d2ed66e4107ef27d05aef682c68af5952af7690}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAggs-that-spill patch introduced a perf regression affecting classic in-memory HashAggs: "unnecessary" attributes were removed before spilling, which is pretty much wasted effort when we don't spill]<br />
** Original commit: {{PgCommitURL|1f39bce0}} <br />
** Owner: Jeff Davis<br />
** Fixed at: {{PgCommitURL|2302302236a0c7aeba3377d78dd9d80ba53247df}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2Bfd4k5_pPAYRTDrO2PbtTOe0eHQpBvuqmCr8ic39uTNmR49Eg%40mail.gmail.com Replication slot spill statistics in the wrong place]<br />
** Original commit: {{PgCommitURL|9290ad198b1}}<br />
** Owner: Tomas Vondra, Amit Kapila<br />
** Feature has been reverted<br />
** Fixed/reverted at: {{PgCommitURL|d973747281caece520236e93d255c654cc613ec9}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com EXPLAIN ANALYZE's non-text output should consistently include all fields for hash aggregate, meaning fields "not applicable" to text format output should be shown as 0]<br />
** Owner: David Rowley<br />
** Fixed at: {{PgCommitURL|40efbf8706cdd96e06bc4d1754272e46d9857875}}<br />
<br />
* [https://www.postgresql.org/message-id/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com min_safe_lsn column in pg_replication_slots view]<br />
** Fixed at: {{PgCommitURL|c54b5891f415df36809de1aeb97e4574d5456d69}}<br />
<br />
* [https://www.postgresql.org/message-id/2895b53b033c47ccb22972b589050dd9@EX13D05UWC001.ant.amazon.com pg_stat_statements + track_planning performance regression]<br />
** Fixed at: {{PgCommitURL|d1763ea8c9c32837d373a196ed0c2e1256a55824}}<br />
** Owner: Fujii Masao<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
** The deduplication feature will [https://www.postgresql.org/message-id/CAH2-Wzm1u8HmCamGj2LmtvUudzai5qDJryTotu++JLLD9KVMRw@mail.gmail.com remain enabled by default].<br />
<br />
* [https://www.postgresql.org/message-id/flat/a9408304-4381-a5af-d259-e55d349ae4ce@2ndquadrant.com rethink libpq's default min SSL version]<br />
** Commit: {{PgCommitURL|6e682f61a5bdb08164a805419144318db6b7229f}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/8d55969f-ba37-b89a-6494-e9322ccdb35d%40oss.nttdata.com Review for GetWALAvailability()]<br />
** Commit: {{PgCommitURL|b8fd4e02c6d01183bf6def5897ad6cf7766bfff4}}<br />
<br />
* [https://www.postgresql.org/message-id/f91de4fb-a7ab-b90e-8132-74796e049d51%40oss.nttdata.com Assertion failure in pg_copy_logical_replication_slot()]<br />
** Commit: {{PgCommitURL|a82ba066ea217e7fe4da3c20ced01e7ca976a351}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040624.GA17995@telsasoft.com hashagg spill to disk] Owner: Jeff Davis<br />
** Commit: {{PgCommitURL|d73e9a57bf5bd977d9bf36bc07c77a1acf45e35b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200717153540.GA17100@alvherre.pgsql Should pg_stat_activity.leader_pid be NULL for leaders themselves?]<br />
** Commit: {{PgCommitURL|11a68e4b53ffccf336a2faf5fa380acda28e880b}}<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Commit: {{PgCommitURL|fd49d53807575e009f7b66771d48c9356344d7d1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Commit: {{PgCommitURL|9bdb300dedf086cc54edf740088208e6b24307ef}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: June 25, 2020<br />
* Beta 3: August 13, 2020<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35084PostgreSQL 13 Open Items2020-07-01T00:20:46Z<p>Davidrowley: Mark "explain non-text format should always include all fields, even if zero" fixed for hashagg only</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAgg perf regression]<br />
** Owner: Jeff Davis<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040358.GZ17995@telsasoft.com incremental sort] Owner: James Coleman, Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAB%3DJe-GOWMj1PTPkeUhjqQp-4W3%3DnW-pXe2Hjax6rJFffB5_Aw%40mail.gmail.com Initiating Physical Replication on a Logical Replication Session]<br />
<br />
* [https://www.postgresql.org/message-id/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com min_safe_lsn column in pg_replication_slots view]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/2895b53b033c47ccb22972b589050dd9@EX13D05UWC001.ant.amazon.com pg_stat_statements + track_planning performance regression]<br />
** Owner: Fujii Masao<br />
<br />
== Decisions to Re-Check Mid Beta ==<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for enable_hashagg_disk]<br />
** Owner: Jeff Davis<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table.]<br />
** Affects v12 and probably v11 (partition pruning)<br />
* [https://www.postgresql.org/message-id/20200415233848.saqp72pcjv2y6ryi%40alap3.anarazel.de xid wraparound danger due to INDEX_CLEANUP false.]<br />
** Affects v12<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
** Fixed at: {{PgCommitURL|a44dd932ff3816de7fe0414063cfcc5656117c3a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/a9408304-4381-a5af-d259-e55d349ae4ce@2ndquadrant.com rethink libpq's default min SSL version]<br />
** Commit: {{PgCommitURL|6e682f61a5bdb08164a805419144318db6b7229f}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/8d55969f-ba37-b89a-6494-e9322ccdb35d%40oss.nttdata.com Review for GetWALAvailability()]<br />
** Commit: {{PgCommitURL|b8fd4e02c6d01183bf6def5897ad6cf7766bfff4}}<br />
<br />
* [https://www.postgresql.org/message-id/f91de4fb-a7ab-b90e-8132-74796e049d51%40oss.nttdata.com Assertion failure in pg_copy_logical_replication_slot()]<br />
** Commit: {{PgCommitURL|a82ba066ea217e7fe4da3c20ced01e7ca976a351}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040624.GA17995@telsasoft.com hashagg spill to disk] Owner: Jeff Davis<br />
** Commit: {{PgCommitURL|d73e9a57bf5bd977d9bf36bc07c77a1acf45e35b}}<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Commit: {{PgCommitURL|fd49d53807575e009f7b66771d48c9356344d7d1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Commit: {{PgCommitURL|9bdb300dedf086cc54edf740088208e6b24307ef}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: June 25, 2020<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35078PostgreSQL 13 Open Items2020-06-25T09:17:49Z<p>Davidrowley: /* Open Issues */ Add link to new thread about EXPLAIN properties</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAgg perf regression]<br />
** Owner: Jeff Davis<br />
<br />
* [https://www.postgresql.org/message-id/20200615132941.GN52676@paquier.xyz Failures with installcheck and low work_mem value in 13~]<br />
** Owners: Alexander Korotkov, Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvo_dmNozQQTmN-2jGp1vT%3Ddxx7Q0vd%2BMvD1cGpv2HU%3DSg%40mail.gmail.com explain non-text format should always include all fields, even if zero]<br />
** [https://www.postgresql.org/message-id/20200619040358.GZ17995@telsasoft.com incremental sort] Owner: James Coleman, Tomas Vondra<br />
** [https://www.postgresql.org/message-id/20200619040624.GA17995@telsasoft.com hashagg spill to disk] Owner: Jeff Davis<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAB%3DJe-GOWMj1PTPkeUhjqQp-4W3%3DnW-pXe2Hjax6rJFffB5_Aw%40mail.gmail.com Initiating Physical Replication on a Logical Replication Session]<br />
<br />
* [https://www.postgresql.org/message-id/9ddfbf8c-2f67-904d-44ed-cf8bc5916228@oss.nttdata.com min_safe_lsn column in pg_replication_slots view]<br />
** Owner: Alvaro Herrera<br />
<br />
== Decisions to Re-Check Mid Beta ==<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for enable_hashagg_disk]<br />
** Owner: Jeff Davis<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table.]<br />
** Affects v12 and probably v11 (partition pruning)<br />
* [https://www.postgresql.org/message-id/20200415233848.saqp72pcjv2y6ryi%40alap3.anarazel.de xid wraparound danger due to INDEX_CLEANUP false.]<br />
** Affects v12<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
** Fixed at: {{PgCommitURL|a44dd932ff3816de7fe0414063cfcc5656117c3a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/8d55969f-ba37-b89a-6494-e9322ccdb35d%40oss.nttdata.com Review for GetWALAvailability()]<br />
** Commit: {{PgCommitURL|b8fd4e02c6d01183bf6def5897ad6cf7766bfff4}}<br />
<br />
* [https://www.postgresql.org/message-id/f91de4fb-a7ab-b90e-8132-74796e049d51%40oss.nttdata.com Assertion failure in pg_copy_logical_replication_slot()]<br />
** Commit: {{PgCommitURL|a82ba066ea217e7fe4da3c20ced01e7ca976a351}}<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Commit: {{PgCommitURL|fd49d53807575e009f7b66771d48c9356344d7d1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Commit: {{PgCommitURL|9bdb300dedf086cc54edf740088208e6b24307ef}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: June 25, 2020<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35039PostgreSQL 13 Open Items2020-06-18T03:41:32Z<p>Davidrowley: /* Open Issues */ Add new issue for explain analyze hashagg output</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20200606041146.slqfg7cuptx27tuy@alap3.anarazel.de HashAgg perf regression]<br />
** Owner: Jeff Davis<br />
<br />
* [https://www.postgresql.org/message-id/20200606001926.zin5getvvhqppnm2%40alap3.anarazel.de Global barrier w/disable atomics leads to spinlock use in signal handlers]<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/20200615131405.GM52676@paquier.xyz Failures with wal_consistency_checking - SPGist/VACUUM_REDIRECT record]<br />
<br />
* [https://www.postgresql.org/message-id/20200615132941.GN52676@paquier.xyz Failures with installcheck and low work_mem value in 13~]<br />
** Owners: Alexander Korotkov, Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpEKbfZa18mM1TD7qV6PG+w97pwCWq5tVD0dX7e11gRJw@mail.gmail.com Missing EXPLAIN ANALYZE properties for parallel HashAgg plans]<br />
** Owner: David Rowley<br />
<br />
== Decisions to Re-Check Mid Beta ==<br />
<br />
* Review the decision to enable deduplication by default (i.e. use 'on' as the default setting for the 'deduplicate_items' B-Tree storage parameter).<br />
** Commit: {{PgCommitURL|0d861bbb}}<br />
** Owner: Peter Geoghegan<br />
<br />
* [https://postgr.es/m/9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com Default setting for enable_hashagg_disk]<br />
** Owner: Jeff Davis<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6k2KoQ%3DWjvNdW_Jyct7HuoVvqdgj-bEiXavS1BqOPzi%2Bw%40mail.gmail.com ERROR with FOR UPDATE/SHARE for partitioned table.]<br />
** Affects v12 and probably v11 (partition pruning)<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200217225333.GA30974@alvherre.pgsql pg_dump does not reproduce ALTER ... DEPENDS ON EXTENSION]<br />
** Fixed at: {{PgCommitURL|5fc703946bf3b18642ce83b937671d254a8ac5b5}}<br />
** Still affected in previous versions, but only patched to PG13<br />
<br />
* [https://www.postgresql.org/message-id/20200328151721.GB12854%40nol pg_stat_statements doesn't report buffer consumption from parallel utility workers]<br />
** Commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}} (parallel btree index build) - Fixed at 5c71362174eb56676f8b91c73ec066dd5513fd4b<br />
** Commit: {{PgCommitURL|40d964ec997f64227bc0ff5e058dc4a5770a70a9}} (parallel vacuum) - Fixed at 3a5e22138a8d014590834eb808c99a436c246aab<br />
<br />
* [https://www.postgresql.org/message-id/flat/21519.1585272409%40sss.pgh.pa.us Intermittent assertion failure in SyncRepGetSyncStandbysPriority]<br />
** Fixed at: {{PgCommitURL|f332241a60aa9c0945d74642cb3dbcbc11621154}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200408152412.GZ2228%40telsasoft.com DETACH PARTITION and FOR EACH ROW triggers on partitioned tables]<br />
** Fixed at: {{PgCommitURL|afccd76f1ccef73a341e9b0c6efb29a429f35aa4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200323165059.GA24950%40alvherre.pgsql hash node details apparently accessing pfreed allocation]<br />
** Commit: {{PgCommitURL|3fc6e2d7f}}<br />
** Fixed at: {{PgCommitURL|5c27bce7f3}}, {{PgCommitURL|969f9d0b4}}<br />
** Fixed in backbranches by: {{PgCommitURL|5c27bce7f}} et al<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w%40mail.gmail.com Crash involving logical replication REPLICA IDENTITY FULL and subscribe+publish]<br />
** Affects v10-master<br />
** Fixed at: {{PgCommitURL|7ccb2f54d9f3f3c5b4ac092d62c846b02a47f8d5}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAJGNTeO93u-5APMga6WH41eTZ3Uee9f3s8dCpA-GSSqNs1b=Ug@mail.gmail.com segmentation fault using currtid and partitioned tables]<br />
** Issue with tableam (since v12)<br />
** Fixed at: {{PgCommitURL|e786be5fcb257a09b05bd8e509c8d1b82e626352}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 13beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BhUKGJUw08dPs_3EUcdO6M90GnjofPYrWp4YSLaBkgYwS-AqA%40mail.gmail.com 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.<br />
** Commit: {{PgCommitURL|b09ff536}}<br />
** No one argued strongly in favour of changing it, so let's leave it as it is.<br />
<br />
* [https://postgr.es/m/CAB=Je-GOWMj1PTPkeUhjqQp-4W3=nW-pXe2Hjax6rJFffB5_Aw@mail.gmail.com SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762]<br />
** Commit: {{PgCommitURL|10ffe0fa}}<br />
<br />
* [https://www.postgresql.org/message-id/e9766d71-8655-ac86-bdf6-77e0e7169977@2ndquadrant.com Moving fe_archive.c to src/fe_utils/]<br />
** Commit: {{PgCommitURL|a3b2bf1f}}<br />
<br />
* [https://www.postgresql.org/message-id/20200519151202.u2p2gpiawoaznsv2@development Trouble with hashagg spill I/O pattern and costing]<br />
** Fixed at: {{PgCommitURL|896ddf9b3cd7dcf70e43f733ae8fec5dfe6e31af}}<br />
** Fixed at: {{PgCommitURL|4cad2534da6d17067d98cf04be2dfc1bda8f2cd0}}<br />
<br />
* [https://postgr.es/m/99b2eab335c1592c925d8143979c8e9e81e1575f.camel@j-davis.com Possible regression with FORTIFY_SOURCE]<br />
** Fixed at: {{PgCommitURL|1fbb6c93df30801f83c6804ab7befde3cdefe677}}<br />
<br />
* [https://www.postgresql.org/message-id/8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com GUC naming]<br />
** Fixed at: {{PgCommitURL|13e0fa7ae50cd0e91158877dba37098492b234e8}}<br />
<br />
=== resolved before 13beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20200406025651.fpzdb5yyb7qyhqko@alap3.anarazel.de 2pc leaks fds]<br />
** Commit: {{PgCommitURL|0dc8ead4}}<br />
** Owner: Alvaro Herrera<br />
** Fixed at {{PgCommitURL|91c40548}} and {{PgCommitURL|b060dbe000}}<br />
<br />
* [https://www.postgresql.org/message-id/20200408.093710.447591748588426656.horikyota.ntt@gmail.com Two issues related to slot-invalidation ]<br />
** Crash on logical-walsender startup after slot invalidation<br />
*** Fixed at {{PgCommitURL|d0abe78d84274cc203f3d117b8006dc2164ca31a}}<br />
** Checkpointer missses requests when slot invalidation occurs<br />
*** Fixed at {{PgCommitURL|1816a1c6ffe46782eee9a16a974b4aa3f4b8457b}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200310190142.GB29065%40telsasoft.com#78420835db672ec62b83e00789efb367 "backend type in log_line_prefix": Update file_fdw]<br />
** Fixed at {{PgCommitURL|0830d21f5b01064837dc8bd910ab31a5b7a1101a}}<br />
<br />
* [https://www.postgresql.org/message-id/753391579708726@iva3-77ae5995f07f.qloud-c.yandex.net Rework handling of wal_receiver_create_temp_slot to fit with WAL receiver architecture]<br />
** Fixed at {{PgCommitURL|092c6936de49e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAMbWs4_maqdBnRR4x01pDpoV-CiQ%2BRvMQaPm4JoTPbA%3DmZmhMw%40mail.gmail.com Negative cost is seen for plan node: Hash agg spill to disk]<br />
** Fixed at: {{PgCommitURL|7351bfeda33b60b69c15791c7eb77a127546df26}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200315234833.GA31110%40alvherre.pgsql#c50e981ed9dd24101c0ec054d5511d7f control max length of parameter values logged]<br />
** Fixed at {{PgCommitURL|0b34e7d307e6a142ee94800e6d5f3e73449eeffd}}<br />
<br />
* [https://www.postgresql.org/message-id/16346-6210ad7a0ea81be1@postgresql.org BUG #16346: pg_upgrade fails on a trigger with a comment]<br />
** Fixed at: {{PgCommitURL|a9d70c108786712a1023c65e360602edf7bafbf4}}<br />
<br />
* [https://postgr.es/m/ec63d70b668818255486a83ffadc3aec492c1f57.camel%40j-davis.com Tweak memory accounting for Hash Aggregation]<br />
** Fixed at: {{PgCommitURL|50a38f65177ea7858bc97f71ba0757ba04c1c167}}<br />
<br />
* [https://www.postgresql.org/message-id/20200410080910.GZ1606@paquier.xyz pg_basebackup, manifests and backends older than ~12]<br />
** Fixed at: {{PgCommitURL|542d7817f774ea9d94798eb95cdf250d4f1527d9}}<br />
<br />
* [https://www.postgresql.org/message-id/58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com Vacuum o/p with (full 1, parallel 0) option throwing an error]<br />
** Fixed at: {{PgCommitURL|24d2d38b1eb86c0b410ad0f07f66566a83c6f05c}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20200411214639.GK2228%40telsasoft.com sqlsmith crash incremental sort]<br />
** Fixed at: {{PgCommitURL|de0dc1a84710f127fdd40f87e783797cc2d69a77}}<br />
<br />
* [https://www.postgresql.org/message-id/2266d9f2-70fe-3156-8fea-e3403461cbdc@2ndquadrant.com Rename libpq parameters ssl{min|max}protocolversion to ssl_{min|max}_protocol_version?]<br />
** Fixed at: {{PgCommitURL|401aad67045b2d467571b54abe229fdd115a228c}}<br />
<br />
* [https://www.postgresql.org/message-id/20200402054120.GC14618@telsasoft.com consistency of explain output: two spaces, equals vs colons, semicolons (WAL)]<br />
** Fixed at: {{PgCommitURL|69bfaf2e1de49de76d7dec1c45511932a5ef502b}}<br />
<br />
* [https://www.postgresql.org/message-id/20200414065336.GI1492@paquier.xyz Incremental sorts and EXEC_FLAG_REWIND]<br />
** Fixed at: {{PgCommitURL|c4427226483c78618ba45eff34917400a77718a5}}<br />
<br />
* consistency of explain output: two spaces, equals vs colons, semicolons (incremental sort)<br />
** [https://www.postgresql.org/message-id/20200407042521.GH2228%40telsasoft.com incremental sort]<br />
** Fixed at: {{PgCommitURL|6a918c3ac8a6b1d8b53cead6fcb7cbd84eee5750}}<br />
<br />
* [https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se Naming issue with client-side sslpassword hook]<br />
** Fixed at: {{PgCommitURL|36d1087611bf96b0cd716666fc8c4a2d168fa501}}<br />
<br />
* [https://postgr.es/m/21247.1589296570@sss.pgh.pa.us Naming issues for wait events, and particularly SLRU caches]<br />
** Fixed at: {{PgCommitURL|3048898e73c75f54bb259323382e0e7f6368cb6f}} and predecessor patches<br />
<br />
* [https://postgr.es/m/20200515090817.GA212736@paquier.xyz pg_stat_wal_receiver and flushedUpto/writtenUpto]<br />
** Fixed at: {{PgCommitURL|2c8dd05d6cbc86b7ad21cfd7010e041bb4c3950b}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2020 ('''Last Day to Commit Features''')<br />
* Beta 1: May 21, 2020<br />
* Beta 2: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33636PostgreSQL 12 Open Items2019-07-10T21:33:44Z<p>Davidrowley: Marked "BulkInsertStates and copy.c with partitioned tables" as fixed</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi GiST Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** Commit {{PgCommitURL|7df159a620b760e289f1795b13542ed1b3e13b87}} Author: Heikki Linnakangas<br />
* [https://postgr.es/m/CAPpHfdvGVegF_TKKRiBrSmatJL2dR9uwFCuR%2BteQ_8tEXU8mxg%40mail.gmail.com Hash join explain can fail with "bogus varno: 65000"]<br />
** Commit {{PgCommitURL|5f32b29c18195299e90c1fb6c8945e9a46d772d2}} Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/aed6cc9f-98f3-2693-ac81-52bb0052307e%402ndquadrant.com postgresql.auto.conf file with duplicate entries not handled properly]<br />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<br />
* [https://www.postgresql.org/message-id/73436355-6432-49B1-92ED-1FE4F7E7E100@finefun.com.au virtual tuple table slot does not have system attributes]<br />
** Commit {{PgCommitURL|277cb789836b5ddf81aabb80c2058268c70e2f36}} Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/CAH2-WznCNvhZpxa__GqAa1fgQ9uYdVc=_apArkW2nc-K3O7_NA@mail.gmail.com Adversarial/pathological case for new nbtree split point choice logic]<br />
** Commit {{PgCommitURL|fab2502433870d98271ba8751f3794e2ed44140a}} Author: Peter Geoghegan<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD/v12 by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
* [https://www.postgresql.org/message-id/20190618231233.GA27470@telsasoft.com Statistics with inheritance cause ANALYZE failures]<br />
** [https://www.postgresql.org/message-id/20190618235755.GA17759@telsasoft.com test case]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Fixed in: {{PgCommitURL|2657283256f1cab53d09d2c7db1ce9b7065193a0}}<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** Fixed in {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** Back-patched to v10; back-patching further is unattractive from both risk and work-required standpoints<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
** Fixed in: {{PgCommitURL|ce59b75d449d9152667ce3e9eab33ef2872bfd98}}<br />
* [https://www.postgresql.org/message-id/20190611061115.njjwkagvxp4qujhp%40alap3.anarazel.de check_recovery_target_lsn() does a PG_CATCH without a throw]<br />
** Commit {{PgCommitURL|2dedf4d9a899b36d1a8ed29be5efbd1b31a8fe85}} Author: Peter Eisentraut<br />
** Fixed in: {{PgCommitURL|21f428ebde39339487c271a830fed135d6032d73}}<br />
* [https://www.postgresql.org/message-id/7586.1560540361@sss.pgh.pa.us psql error messages are now too verbose]<br />
** Commit {{PgCommitURL|cc8d41511721d25d557fc02a46c053c0a602fed0}} Author: Peter Eisentraut<br />
** Fixed in: {{PgCommitURL|3f3542621f131379e32e9283d40853cb6d03a97f}}<br />
* [https://www.postgresql.org/message-id/20190607165105.vn4bl6piofroj3um@alap3.anarazel.de BulkInsertStates and copy.c with partitioned tables]<br />
** Fixed in: {{PgCommitURL|b8ef33b2d14519da0d038e9d63f51a6714ef764a}}<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Fixed in: {{PgCommitURL|a36c84c3e4a9bee6baa7}}<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
** Fixed in: {{PgCommitURL|f73293aba4d43e48707e361b2b1ef1465fef46e0}}<br />
* [https://www.postgresql.org/message-id/20190601191007.GC1905@paquier.xyz psql completion bugs with access methods]<br />
** Fixed in: {{PgCommitURL|0240a00fbd4fd14f577edf8d36a032237fd0b9cb}}<br />
* [https://www.postgresql.org/message-id/15832-b1bf336a4ee246b5@postgresql.org COPY into a partitioned table breaks its indexes]<br />
** Fixed in: {{PgCommitURL|56b3b3838284f53c83556592e60688522155f57f}}<br />
* [https://www.postgresql.org/message-id/20190607043415.GE1736@paquier.xyz be-gssapi-common.h not in correct location]<br />
** Fixed in: {{PgCommitURL|35b2d4bc0eb5d61a2a294ccb6b2e4abdad307604}}<br />
* [https://www.postgresql.org/message-id/CAJrrPGcAxsMM7n__HJRPBrh7Y6ruU6LetfPD=cPGeW=G49na0g@mail.gmail.com pg_basebackup failure after setting default_table_access_method option]<br />
** Fixed in: {{PgCommitURL|fff2a7d7bd09db38e1bafc1303c29b10a9805dc0}}<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|73b8c3bd2889fed986044e15aefd0911f96ccdd3}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warn about using too many partitions]<br />
** Fixed in: {{PgCommitURL|e788e849addd56007a0e75f3b5514f294a0f3bca}}<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Fixed by {{PgCommitURL|6cbfb784c3c91146148a76d50cda6f69ae6a79fb}} et seq<br />
* [https://www.postgresql.org/message-id/20190527203713.GA58392@gust.leadboat.com \connect uses the same IP as the existing connection, docs no longer match behavior, etc.]<br />
** Commit {{PgCommitURL|6e5f8d4}} Author: Fabien Coelho<br />
** Fixed by {{PgCommitURL|313f56ce2d1b9dfd3483e4f39611baa27852835a}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}, the necessary changes are too big for v12<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: June 20, 2019<br />
* beta3: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33567PostgreSQL 12 Open Items2019-06-11T20:15:10Z<p>Davidrowley: Resolve lack of warning about too many partitions.</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Commit {{PgCommitURL|7300a699502fe5432b05fbc75baca534b080bebb}}, Author: Tomas Vondra<br />
* [https://www.postgresql.org/message-id/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi GiST Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** Commit {{PgCommitURL|7df159a620b760e289f1795b13542ed1b3e13b87}} Author: Heikki Linnakangas<br />
* [https://www.postgresql.org/message-id/20190527203713.GA58392@gust.leadboat.com \connect uses the same IP as the existing connection, docs no longer match behavior, etc.]<br />
** Commit {{PgCommitURL|6e5f8d4}} Author: Fabien Coelho<br />
* [https://www.postgresql.org/message-id/20190607165105.vn4bl6piofroj3um@alap3.anarazel.de BulkInsertStates and copy.c with partitioned tables]<br />
* [https://www.postgresql.org/message-id/20190611061115.njjwkagvxp4qujhp%40alap3.anarazel.de check_recovery_target_lsn() does a PG_CATCH without a throw]<br />
** Commit {{PgCommitURL|2dedf4d9a899b36d1a8ed29be5efbd1b31a8fe85}} Author: Peter Eisentraut<br />
* [https://postgr.es/m/CAPpHfdvGVegF_TKKRiBrSmatJL2dR9uwFCuR%2BteQ_8tEXU8mxg%40mail.gmail.com Hash join explain can fail with "bogus varno: 65000"]<br />
** Commit {{PgCommitURL|5f32b29c18195299e90c1fb6c8945e9a46d772d2}} Author: Andres Freund<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Fixed in: {{PgCommitURL|2657283256f1cab53d09d2c7db1ce9b7065193a0}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Fixed in: {{PgCommitURL|a36c84c3e4a9bee6baa7}}<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
** Fixed in: {{PgCommitURL|f73293aba4d43e48707e361b2b1ef1465fef46e0}}<br />
* [https://www.postgresql.org/message-id/20190601191007.GC1905@paquier.xyz psql completion bugs with access methods]<br />
** Fixed in: {{PgCommitURL|0240a00fbd4fd14f577edf8d36a032237fd0b9cb}}<br />
* [https://www.postgresql.org/message-id/15832-b1bf336a4ee246b5@postgresql.org COPY into a partitioned table breaks its indexes]<br />
** Fixed in: {{PgCommitURL|56b3b3838284f53c83556592e60688522155f57f}}<br />
* [https://www.postgresql.org/message-id/20190607043415.GE1736@paquier.xyz be-gssapi-common.h not in correct location]<br />
** Fixed in: {{PgCommitURL|35b2d4bc0eb5d61a2a294ccb6b2e4abdad307604}}<br />
* [https://www.postgresql.org/message-id/CAJrrPGcAxsMM7n__HJRPBrh7Y6ruU6LetfPD=cPGeW=G49na0g@mail.gmail.com pg_basebackup failure after setting default_table_access_method option]<br />
** Fixed in: {{PgCommitURL|fff2a7d7bd09db38e1bafc1303c29b10a9805dc0}}<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|73b8c3bd2889fed986044e15aefd0911f96ccdd3}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warn about using too many partitions]<br />
** Fixed in: {{PgCommitURL|e788e849addd56007a0e75f3b5514f294a0f3bca}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}, the necessary changes are too big for v12<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33556PostgreSQL 12 Open Items2019-06-08T19:42:49Z<p>Davidrowley: Mark statistical aggregate problem as fixed. Should have been marked as fixed weeks ago.</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Commit {{PgCommitURL|7300a699502fe5432b05fbc75baca534b080bebb}}, Author: Tomas Vondra<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}<br />
** ... but there's still interest in trying to get this to work for v12<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warn about using too many partitions]<br />
* [https://www.postgresql.org/message-id/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi GiST Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** Commit {{PgCommitURL|7df159a620b760e289f1795b13542ed1b3e13b87}} Author: Heikki Linnakangas<br />
* [https://www.postgresql.org/message-id/20190607043415.GE1736@paquier.xyz be-gssapi-common.h not in correct location]<br />
** Commit {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}} Author: Stephen Frost<br />
* [https://www.postgresql.org/message-id/20190527203713.GA58392@gust.leadboat.com \connect uses the same IP as the existing connection, docs no longer match behavior, etc.]<br />
** Commit {{PgCommitURL|6e5f8d4}} Author: Fabien Coelho<br />
* [https://www.postgresql.org/message-id/CAJrrPGcAxsMM7n__HJRPBrh7Y6ruU6LetfPD=cPGeW=G49na0g@mail.gmail.com pg_basebackup failure after setting default_table_access_method option]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Fixed in: {{PgCommitURL|2657283256f1cab53d09d2c7db1ce9b7065193a0}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Fixed in: {{PgCommitURL|a36c84c3e4a9bee6baa7}}<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
** Fixed in: {{PgCommitURL|f73293aba4d43e48707e361b2b1ef1465fef46e0}}<br />
* [https://www.postgresql.org/message-id/20190601191007.GC1905@paquier.xyz psql completion bugs with access methods]<br />
** Fixed in: {{PgCommitURL|0240a00fbd4fd14f577edf8d36a032237fd0b9cb}}<br />
* [https://www.postgresql.org/message-id/15832-b1bf336a4ee246b5@postgresql.org COPY into a partitioned table breaks its indexes]<br />
** Fixed in: {{PgCommitURL|56b3b3838284f53c83556592e60688522155f57f}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33545PostgreSQL 12 Open Items2019-06-05T07:45:23Z<p>Davidrowley: Mark COPY FROM partitioned table item as fixed</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Commit {{PgCommitURL|a9c35cf85ca1ff72f16f0f10d7ddee6e582b62b8}}, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Commit {{PgCommitURL|7300a699502fe5432b05fbc75baca534b080bebb}}, Author: Tomas Vondra<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}<br />
** ... but there's still interest in trying to get this to work for v12<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Commit {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}} Author: Alvaro Herrera<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warn about using too many partitions]<br />
* [https://www.postgresql.org/message-id/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi GiST Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** Commit {{PgCommitURL|7df159a620b760e289f1795b13542ed1b3e13b87}} Author: Heikki Linnakangas<br />
* [https://www.postgresql.org/message-id/20190604014630.GH1529@paquier.xyz be-gssapi-common.h not in correct location]<br />
** Commit {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}} Author: Stephen Frost<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
** Fixed in: {{PgCommitURL|f73293aba4d43e48707e361b2b1ef1465fef46e0}}<br />
* [https://www.postgresql.org/message-id/20190601191007.GC1905@paquier.xyz psql completion bugs with access methods]<br />
** Fixed in: {{PgCommitURL|0240a00fbd4fd14f577edf8d36a032237fd0b9cb}}<br />
* [https://www.postgresql.org/message-id/15832-b1bf336a4ee246b5@postgresql.org COPY into a partitioned table breaks its indexes]<br />
** Fixed in: {{PgCommitURL|56b3b3838284f53c83556592e60688522155f57f}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33501PostgreSQL 12 Open Items2019-05-24T04:40:52Z<p>Davidrowley: /* Open Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Commit {{PgCommitURL|a9c35cf85ca1ff72f16f0f10d7ddee6e582b62b8}}, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Commit {{PgCommitURL|7300a699502fe5432b05fbc75baca534b080bebb}}, Author: Tomas Vondra<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}<br />
** ... but there's still interest in trying to get this to work for v12<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Commit {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}} Author: Alvaro Herrera<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warn about using too many partitions]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33500PostgreSQL 12 Open Items2019-05-24T04:40:31Z<p>Davidrowley: /* Open Issues */ Added items about lack of too many partitions warning in docs</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Commit {{PgCommitURL|a9c35cf85ca1ff72f16f0f10d7ddee6e582b62b8}}, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Commit {{PgCommitURL|7300a699502fe5432b05fbc75baca534b080bebb}}, Author: Tomas Vondra<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}<br />
** ... but there's still interest in trying to get this to work for v12<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Commit {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}} Author: Alvaro Herrera<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warning about using too many partitions]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PgCon_2019_Developer_Meeting&diff=33361PgCon 2019 Developer Meeting2019-04-16T22:01:52Z<p>Davidrowley: /* RSVPs */ Added David Rowley</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 28 May, 2019 at the University of Ottawa, prior to pgCon 2019. In order to keep the numbers manageable, this meeting is by '''invitation only'''.<br />
<br />
The invitation list for the meeting has changed this year to include representatives from various project sub-teams, for example, packagers, the release team, Code of Conduct committee and more.<br />
<br />
As at last years event, an Unconference will be held on Wednesday for in-depth discussion of technical topics.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Define the schedule for the 13.0 release cycle<br />
* Address any proposed timing, policy, or procedure issues<br />
* Receive updates from project sub-teams on their activities and discuss any resulting issues or concerns.<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
<br />
== Time & Location ==<br />
<br />
The meeting will be:<br />
<br />
* 9:00AM to 12PM<br />
* DMS TBC<br />
* University of Ottawa.<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be after the meeting.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname). Note that we can accommodate a '''maximum of 30'''!<br />
<br />
# Joe Conway<br />
# Jeff Davis<br />
# Andrew Dunstan<br />
# Peter Eisentraut<br />
# Andres Freund<br />
# Stephen Frost<br />
# Peter Geoghegan<br />
# Devrim Gündüz<br />
# Robert Haas<br />
# Magnus Hagander<br />
# Stacey Haysler (present for CoC report and discussion only)<br />
# Álvaro Herrera<br />
# Amit Kapila<br />
# Jonathan Katz<br />
# Alexander Korotkov<br />
# Tom Lane<br />
# Heikki Linnakangas<br />
# Noah Misch<br />
# Bruce Momjian<br />
# Thomas Munro<br />
# Dave Page<br />
# Michael Paquier<br />
# David Rowley<br />
# Tomas Vondra<br />
# Robert Treat<br />
<br />
<br />
The following people will not be in Ottawa, and do not plan to attend:<br />
<br />
* Christoph Berg<br />
* Vik Fearing<br />
* Andreas Scherbaum<br />
* Sarah Conway Schnurr<br />
* Ilya Kosmodemiansky<br />
<br />
== Agenda Items ==<br />
<br />
* 13.0 release and commitfest schedule (Dave)<br />
* Contributor Recognition (Andres, happy to share / pass, but should be discussed)<br />
** [https://www.postgresql.org/community/contributors/ contributors] page update - how well is it working?<br />
** should the developer meeting serve as recognition? <br />
* The Evolving Developer Meeting: Goals & What We Want to Accomplish by the end of it? (Jonathan, happy to share)<br />
* SQL standard update (Peter E.)<br />
* ''Please add suggestions for agenda items here. (with your name)''<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave Page<br />
<br />
|-<br />
|09:10 - 09:30<br />
|Code of Conduct report and discussion<br />
|Stacey Haysler<br />
<br />
|- <br />
|09:30 - 09:45<br />
|12.0 release and commitfest schedule<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- <br />
|11:50 - 12:00<br />
|Any other business<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:00<br />
|Lunch<br />
|<br />
<br />
|}<br />
<br />
Note: This timetable is a rough guide only. Items will start as soon as the previous discussion is complete (breaks will not move however). Any remaining time before lunch may be used for Commitfest item triage or other activities.</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33321PostgreSQL 12 Open Items2019-04-15T04:32:15Z<p>Davidrowley: /* Open Issues */ Added EndForeignInsert issue</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** This was fixed in 19455c9f5, but then 3b925e905 made the compatibility argument moot, so should we undo 19455c9f5?<br />
** Patch for that is at [https://www.postgresql.org/message-id/CA+q6zcXx0XHqLsFJLaUU2j5BDiBAHig=YRoBC_YVq7VJGvzBEA@mail.gmail.com]<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Commit: {{PgCommitURL|ca4103025dfe26eaaf6a500dec9170fbb176eebc}}, Author: David Rowley, Owner: Alvaro Herrera<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** [https://www.postgresql.org/message-id/b462ff0c-a846-dce6-b0a7-ab1397e73b98%40lab.ntt.co.jp Patch proposed]<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** [https://commitfest.postgresql.org/23/2072 CF entry]<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilnode]<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
<br />
=== Live issues ===<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33148PostgreSQL 12 Open Items2019-03-17T11:34:14Z<p>Davidrowley: /* Open Issues */ Added item to debate using INFO msgs in ATTACH PARTITION and SET NOT NULL</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** [https://www.postgresql.org/message-id/CAKJS1f_ZaECEN%2BGFtfrepe18ovoqsKNs8YML1BwsnZHr3fdzKQ%40mail.gmail.com Patch exists]<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
=== Fixed issues ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: XXX<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33147PostgreSQL 12 Open Items2019-03-17T11:29:28Z<p>Davidrowley: /* Open Issues */ Added pg_dump is broken for partition tablespaces</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** [https://www.postgresql.org/message-id/CAKJS1f_ZaECEN%2BGFtfrepe18ovoqsKNs8YML1BwsnZHr3fdzKQ%40mail.gmail.com Patch exists]<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
=== Fixed issues ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: XXX<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33146PostgreSQL 12 Open Items2019-03-17T11:26:52Z<p>Davidrowley: /* Open Issues */ Add index locking issue</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** [https://www.postgresql.org/message-id/CAKJS1f_ZaECEN%2BGFtfrepe18ovoqsKNs8YML1BwsnZHr3fdzKQ%40mail.gmail.com Patch exists]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
=== Fixed issues ===<br />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: XXX<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=Open_Items&diff=33145Open Items2019-03-17T11:22:21Z<p>Davidrowley: Repoint at PG12 open items list.</p>
<hr />
<div>#REDIRECT [[PostgreSQL_12_Open_Items]]<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32350PostgreSQL 11 Open Items2018-08-11T06:07:44Z<p>Davidrowley: /* Open Issues */ Added run-time partition pruning unexpected error bug</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/12259.1532117714@sss.pgh.pa.us "could not read block" buildfarm failures]<br />
<br />
* [https://postgr.es/m/CA+TgmobPK_1DKXk8_tyv6McTbPF4bUboVrvF2Qhu+r=-1dHUZQ@mail.gmail.com Use terms such as "JIT compile" rather than "JIT"]<br />
<br />
* [https://www.postgresql.org/message-id/CANEvxPqXGHrvV4VivWHfoi%3DM_1b_UZj4VZ-UMbWG-JNogkJA9A%40mail.gmail.com Memory leak with CALL to Procedure with COMMIT]<br />
<br />
* [https://www.postgresql.org/message-id/CAJGNTeOkdk%3DUVuMugmKL7M%3Dowgt4nNr1wjxMg1F%2BmHsXyLCzFA%40mail.gmail.com Assert failure in run-time pruning]<br />
** Assertion removed in {{PgCommitURL|59ef49d26d2f8724d0788fea0774f786a22ca63d}}, but lack of testing for such cases remains an open issue<br />
<br />
* [https://www.postgresql.org/message-id/20180806183205.GB42466%40jeremyevans.local Fix hints on CREATE PROCEDURE errors]<br />
<br />
* [https://www.postgresql.org/message-id/20180809174931.vjsjxxt2bwoexxsk@depesz.com xact_start meaning when dealing with procedures?]<br />
<br />
* [https://www.postgresql.org/message-id/87in4h98i0.fsf%40ansel.ydns.eu Error during run-time pruning]<br />
** [https://www.postgresql.org/message-id/CAKJS1f8k4U1dseYKQh9ugWF%3DA%2BKqpvw7PCOSf%2BRFv_QXGRoy0g%40mail.gmail.com Patch to resolve the issue]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/16922.1520722108%40sss.pgh.pa.us Intermittent pg_ctl failures on Windows]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-Wzn=j0i8rxCAo6E=tBO9XuYXb8HbUsnW7J_StKON8dDOhQ@mail.gmail.com Parallel CREATE INDEX doesn't have relmapper.c state propogated when reindexing mapped catalog relations during VACUUM FULL.]<br />
** Fixed in: {{PgCommitURL|4974d7f87e62a58e80c6524e49677cb25cc10e12}}<br />
* [https://www.postgresql.org/message-id/20180628150209.n2qch5jtn3vt2xaa@alap3.anarazel.de Failed index build can corrupt relcache contents]<br />
** Fixed in: {{PgCommitURL|b3f919da07540d7c968e8495482336304badcef7}}<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
** Fixed in: {{PgCommitURL|f49a80c481f74fa81}}<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
** Fixed in: {{PgCommitURL|3c64dcb1e35dccbfce531182fa9b9f48bec414ad}}<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
** Fixed in: {{PgCommitURL|0414ac6a1eb2e457c8019c5a558bd72b37dede89}} <br />
* [https://postgr.es/m/CA+q6zcUq2VKFBwgk42Qg2hz-=62c1cB1MCBV6Ocwtj__9=RWtQ@mail.gmail.com LLVM jit and window functions on a temporary table]<br />
** Turned out to be an older bug independent of JIT [https://www.postgresql.org/message-id/CA+q6zcUpGip3pwSZRnYNan1vTiPuuror7OR8pn2snmb5TTdqfQ@mail.gmail.com Report]<br />
** Fixed in: {{PgCommitURL|ff4f88916}}<br />
* [https://www.postgresql.org/message-id/CA+q6zcWO7CeAJtHBxgcHn_hj+PenM=tvG0RJ93X1uEJ86+76Ug@mail.gmail.com LLVM jit and matview]<br />
** Fixed in: {{PgCommitURL|3acc4acd9bcbefbfaf789762950726c6208daf1b}}<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
** Channel binding has been removed from the list of major features. A more generic solution involving as well downgrades like scram -> md5 need to be designed and thought about.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta4 ===<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
** Fixed in {{PgCommitURL|dac7fe13bbf10c249a519d6a41c683c42c7e3312}}<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** Fixed in {{PgCommitURL|1b54e91faabf3764b6786915881e514e42dccf89}}<br />
<br />
* [https://www.postgresql.org/message-id/20180731185813.snlncuzfkn4sfh7i@alap3.anarazel.de Advance replication slot patch broke detection of nonexistant output plugins]<br />
** Broken in {{PgCommitURL|9c7d06d60680c7f00d931233873dee81fdb311c6}}<br />
** Fixed in {{PgCommitURL|7326a7d63801673d3569def65cb7955d6486f254}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOP8fzYtVFWZADq4c=KoTAqgDrHWfng+AnEPEZccyxqxPVbbWQ@mail.gmail.com memory leaks in COPY FROM on partitioned table]<br />
** Fixed in: {{PgCommitURL|34295b87fbbcbaf26280f53f006b20971dbad1f3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6k=udMa_oOXnbHduBwvJ8SnUaQxRLPA=D2+ryYoyT6eeA@mail.gmail.com partition pruning failure]<br />
** Fixed in: {{PgCommitURL|192d1bbf99699de76473184c57fff9ff4b4246f4}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAD__OugYDM3O%2BdyZnnZSbJprSfsGFJcQ1R%3De59T3hcLmDug4_w%40mail.gmail.com unnamed POSIX semaphores are slow]<br />
** Fixed in: {{PgCommitURL|f2db5f3bb0b5d429e9fa5b093936f8524e4192b1}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf165-=+Drw3Voim7M5EjHT1zwPF9BQRjLFQzCzYnNZEiQ@mail.gmail.com wrong query result with jit_above_cost=0]<br />
** Fixed in: {{PgCommitURL|6b4d860311e99621681f25db5db82f88348d8ea6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180723.135748.42558387.horiguchi.kyotaro%40lab.ntt.co.jp Fix calculations on WAL recycling]<br />
** Fixed in {{PgCommitURL|9915735ebb}}<br />
<br />
* [https://www.postgresql.org/message-id/20180628182803.e4632d5a.nagata@sraoss.co.jp Fix error message when trying to alter statistics on included column]<br />
** Fixed in {{PgCommitURL|802b04cb3f}}<br />
<br />
* [https://postgr.es/m/CAFjFpRc7qjLUfXLVBBC_HAnx644sjTYM=qVoT3TJ840HPbsTXw@mail.gmail.com partition pruning doesn't work with IS NULL clause in multikey range partition case]<br />
** Fixed in {{PgCommitURL|fb2b61a21e141843697de7982c9f6485effcd915}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAJ_b94n=UsNVhgs97vCaWEZAMe-tGDRVuZ73oePQH=eaJKGSA@mail.gmail.com Cannot dump foreign key constraints on partitioned table]<br />
** Fixed in {{PgCommitURL|2af39c39df94096ecc593f5a162947e1e994cab3}}<br />
<br />
* {{messageLink|20180711000624.zmeizicibxeehhsg@alvherre.pgsql|TRUNCATE tables referenced by FKs on partitioned tables is broken}}<br />
** Fixed in {{PgCommitURL|727196ced2423008bb25d7775c4e3b7fca063c8b}}<br />
<br />
* {{messageLink|CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com|Server crashed with dense_rank on partition table}}<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
** Fixed in {{PgCommitURL|e60cfcefe635b90bab60e885be689700759a01c6}}<br />
<br />
* {{messageLink|20180618165910.p26vhk7dpq65ix54@alvherre.pgsql|Listing triggers in partitions}}<br />
** Fixed in {{PgCommitURL|bc87f22ef6ef1137909ed7363976c67cf1efa7da}}<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
** Fixed in {{PgCommitURL|42121790ca9b27e01fd0471fdac28ec4a381eaee}}<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
** Fixed in {{PgCommitURL|9069eb95f48c8200f8589faf7adc5e324eed25cd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDrWqycq-w_%2BBx1cjc%2BYUhZ11XTj9rfxNiNDojjBx8Fjw%40mail.gmail.com Failed assertion in GROUPS mode of window function in current HEAD]<br />
** Fixed in {{PgCommitURL|ff4f8891648c804c7c126fdf438257b1e9dc7ca4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
** Fixed in {{PgCommitURL|40ca70ebcc9d0bc1c02937b27c44b2766617e790}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAJ_b942auDRKu22MW+yMxTnSyyAdEoGkUSt+H37-0HcCjdA0w@mail.gmail.com Failed assertion due to procedure created with SECURITY DEFINER option]<br />
** Fixed in {{PgCommitURL|3804e89bd0e94fb412d3eecb2113cc97e0f7310b}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+q6zcWzN9ztCfR47ZwgTr1KLnuO6BAY6FurxXhovP4hxr+yOQ@mail.gmail.com Problem with tupdesc in jsonb_to_recordset]<br />
** Fixed in {{PgCommitURL|4984784f836a061985b356c52253b5d83a0cbe65}}<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
** Fixed in {{PgCommitURL|d89348976c51952293ffe35845c372ffa7e93b47}}<br />
<br />
* [https://www.postgresql.org/message-id/87wotkfju1.fsf%40news-spur.riddles.org.uk crash/assert caused by parameter type changes]<br />
** Fixed in {{PgCommitURL|662d12aea1d697adc4896ff7e5d5cf398c0cd267}}<br />
<br />
=== resolved before 11beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Fixed in: {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}} with fixup {{PgCommitURL|123efbccea}}<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
** Fixed in: {{PgCommitURL|e348e7ae5727}} {{PgCommitURL|1731e3741cbbf8e0b}} {{PgCommitURL|93b6e03ab4794}}<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff]<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
* [https://www.postgresql.org/message-id/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com Performance regression with PostgreSQL 11 and partitioning]<br />
** Fixed in: {{PgCommitURL|7d872c91a3f9d49b56117557cdbb0c3d4c620687}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A%40mail.gmail.com Error during partition index rename]<br />
** Fixed in: {{PgCommitURL|040da42367a5de448ddecf6ee7c09f73580a6b28}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: 9th of August 2018<br />
* beta4: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32251PostgreSQL 11 Open Items2018-07-24T09:58:00Z<p>Davidrowley: /* Open Issues */ Added item for "FailedAssertion on partprune"</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
** [https://www.postgresql.org/message-id/CAA4eK1JW0JVVznGOYcjnii35wyz3dw_sv1H1ANp8hR7D85ZwyQ@mail.gmail.com patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** 3 possible ways to fix. David has sent different patches for all 3. [https://www.postgresql.org/message-id/CAKJS1f9KG5nnOFhigWm4ND5Ut-yU075iJyA%2BACVyQnZ-ZW1Qtw%40mail.gmail.com 1], [https://www.postgresql.org/message-id/CAKJS1f-OYZZJOr7F6eJQ3WK2cspMp13n%3DQHP5V7Vm0wzKYzaxA%40mail.gmail.com 2] and [https://www.postgresql.org/message-id/CAKJS1f9cqoSKS9JVcBKGa2mdn-24YPWc9XLzFDNsmjJMUpth1w%40mail.gmail.com 3]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf165-=+Drw3Voim7M5EjHT1zwPF9BQRjLFQzCzYnNZEiQ@mail.gmail.com wrong query result with jit_above_cost=0]<br />
<br />
* [https://www.postgresql.org/message-id/CA+q6zcWO7CeAJtHBxgcHn_hj+PenM=tvG0RJ93X1uEJ86+76Ug@mail.gmail.com LLVM jit and matview]<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAD__OugYDM3O%2BdyZnnZSbJprSfsGFJcQ1R%3De59T3hcLmDug4_w%40mail.gmail.com unnamed POSIX semaphores are slow]<br />
<br />
* [https://www.postgresql.org/message-id/12259.1532117714@sss.pgh.pa.us "could not read block" buildfarm failures]<br />
<br />
* [https://postgr.es/m/CA+TgmobPK_1DKXk8_tyv6McTbPF4bUboVrvF2Qhu+r=-1dHUZQ@mail.gmail.com Use terms such as "JIT compile" rather than "JIT"]<br />
<br />
* [https://www.postgresql.org/message-id/CANEvxPqXGHrvV4VivWHfoi%3DM_1b_UZj4VZ-UMbWG-JNogkJA9A%40mail.gmail.com Memory leak with CALL to Procedure with COMMIT]<br />
<br />
* [https://www.postgresql.org/message-id/CAOP8fzYtVFWZADq4c=KoTAqgDrHWfng+AnEPEZccyxqxPVbbWQ@mail.gmail.com memory leaks in COPY FROM on partitioned table]<br />
<br />
* [https://www.postgresql.org/message-id/CAJGNTeOkdk%3DUVuMugmKL7M%3Dowgt4nNr1wjxMg1F%2BmHsXyLCzFA%40mail.gmail.com Assert failure in run-time pruning]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/16922.1520722108%40sss.pgh.pa.us Intermittent pg_ctl failures on Windows]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
** Fix in: {{PgCommitURL|f49a80c481f74fa81}}<br />
<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
** Fixed in: {{PgCommitURL|3c64dcb1e35dccbfce531182fa9b9f48bec414ad}}<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
** Fixed in: {{PgCommitURL|0414ac6a1eb2e457c8019c5a558bd72b37dede89}} <br />
<br />
* [https://postgr.es/m/CA+q6zcUq2VKFBwgk42Qg2hz-=62c1cB1MCBV6Ocwtj__9=RWtQ@mail.gmail.com LLVM jit and window functions on a temporary table]<br />
** Turned out to be an older bug independent of JIT [https://www.postgresql.org/message-id/CA+q6zcUpGip3pwSZRnYNan1vTiPuuror7OR8pn2snmb5TTdqfQ@mail.gmail.com Report]<br />
** Fixed in: {{PgCommitURL|ff4f88916}}<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
** Channel binding has been removed from the list of major features. A more generic solution involving as well downgrades like scram -> md5 need to be designed and thought about.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/20180723.135748.42558387.horiguchi.kyotaro%40lab.ntt.co.jp Fix calculations on WAL recycling]<br />
** Fixed in {{PgCommitURL|9915735ebb}}<br />
<br />
* [https://www.postgresql.org/message-id/20180628182803.e4632d5a.nagata@sraoss.co.jp Fix error message when trying to alter statistics on included column]<br />
** Fixed in {{PgCommitURL|802b04cb3f}}<br />
<br />
* [https://postgr.es/m/CAFjFpRc7qjLUfXLVBBC_HAnx644sjTYM=qVoT3TJ840HPbsTXw@mail.gmail.com partition pruning doesn't work with IS NULL clause in multikey range partition case]<br />
** Fixed in {{PgCommitURL|fb2b61a21e141843697de7982c9f6485effcd915}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAJ_b94n=UsNVhgs97vCaWEZAMe-tGDRVuZ73oePQH=eaJKGSA@mail.gmail.com Cannot dump foreign key constraints on partitioned table]<br />
** Fixed in {{PgCommitURL|2af39c39df94096ecc593f5a162947e1e994cab3}}<br />
<br />
* {{messageLink|20180711000624.zmeizicibxeehhsg@alvherre.pgsql|TRUNCATE tables referenced by FKs on partitioned tables is broken}}<br />
** Fixed in {{PgCommitURL|727196ced2423008bb25d7775c4e3b7fca063c8b}}<br />
<br />
* {{messageLink|CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com|Server crashed with dense_rank on partition table}}<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
** Fixed in {{PgCommitURL|e60cfcefe635b90bab60e885be689700759a01c6}}<br />
<br />
* {{messageLink|20180618165910.p26vhk7dpq65ix54@alvherre.pgsql|Listing triggers in partitions}}<br />
** Fixed in {{PgCommitURL|bc87f22ef6ef1137909ed7363976c67cf1efa7da}}<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
** Fixed in {{PgCommitURL|42121790ca9b27e01fd0471fdac28ec4a381eaee}}<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
** Fixed in {{PgCommitURL|9069eb95f48c8200f8589faf7adc5e324eed25cd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDrWqycq-w_%2BBx1cjc%2BYUhZ11XTj9rfxNiNDojjBx8Fjw%40mail.gmail.com Failed assertion in GROUPS mode of window function in current HEAD]<br />
** Fixed in {{PgCommitURL|ff4f8891648c804c7c126fdf438257b1e9dc7ca4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
** Fixed in {{PgCommitURL|40ca70ebcc9d0bc1c02937b27c44b2766617e790}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAJ_b942auDRKu22MW+yMxTnSyyAdEoGkUSt+H37-0HcCjdA0w@mail.gmail.com Failed assertion due to procedure created with SECURITY DEFINER option]<br />
** Fixed in {{PgCommitURL|3804e89bd0e94fb412d3eecb2113cc97e0f7310b}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+q6zcWzN9ztCfR47ZwgTr1KLnuO6BAY6FurxXhovP4hxr+yOQ@mail.gmail.com Problem with tupdesc in jsonb_to_recordset]<br />
** Fixed in {{PgCommitURL|4984784f836a061985b356c52253b5d83a0cbe65}}<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
** Fixed in {{PgCommitURL|d89348976c51952293ffe35845c372ffa7e93b47}}<br />
<br />
=== resolved before 11beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Fixed in: {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}} with fixup {{PgCommitURL|123efbccea}}<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
** Fixed in: {{PgCommitURL|e348e7ae5727}} {{PgCommitURL|1731e3741cbbf8e0b}} {{PgCommitURL|93b6e03ab4794}}<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff]<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
* [https://www.postgresql.org/message-id/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com Performance regression with PostgreSQL 11 and partitioning]<br />
** Fixed in: {{PgCommitURL|7d872c91a3f9d49b56117557cdbb0c3d4c620687}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A%40mail.gmail.com Error during partition index rename]<br />
** Fixed in: {{PgCommitURL|040da42367a5de448ddecf6ee7c09f73580a6b28}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32129PostgreSQL 11 Open Items2018-06-26T23:13:22Z<p>Davidrowley: /* resolved before 11beta2 */ Partition index rename fixed.</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff], awaiting testing<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** 3 possible ways to fix. David has sent different patches for all 3. [https://www.postgresql.org/message-id/CAKJS1f9KG5nnOFhigWm4ND5Ut-yU075iJyA%2BACVyQnZ-ZW1Qtw%40mail.gmail.com 1], [https://www.postgresql.org/message-id/CAKJS1f-OYZZJOr7F6eJQ3WK2cspMp13n%3DQHP5V7Vm0wzKYzaxA%40mail.gmail.com 2] and [https://www.postgresql.org/message-id/CAKJS1f9cqoSKS9JVcBKGa2mdn-24YPWc9XLzFDNsmjJMUpth1w%40mail.gmail.com 3]<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com Server crashed with dense_rank on partition table]<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Introduced by {{PgCommitURL|16828d5c0273b4fe5f10f42588005f16b415b2d8}} (Fast ALTER TABLE ADD COLUMN with a non-NULL default)<br />
** Was this fixed by {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}}? (Allow for pg_upgrade of attributes with missing values) and {{PgCommitURL|123efbccea694626b36ad952086d883fa7469aa9}}? (Mark binary_upgrade_set_missing_value as parallel_unsafe)<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf165-=+Drw3Voim7M5EjHT1zwPF9BQRjLFQzCzYnNZEiQ@mail.gmail.com wrong query result with jit_above_cost=0]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
** Fix in: {{PgCommitURL|f49a80c481f74fa81}}<br />
<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
=== resolved before 11beta2 ===<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
* [https://www.postgresql.org/message-id/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com Performance regression with PostgreSQL 11 and partitioning]<br />
** Fixed in: {{PgCommitURL|7d872c91a3f9d49b56117557cdbb0c3d4c620687}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A%40mail.gmail.com Error during partition index rename]<br />
** Fixed in: {{PgCommitURL|040da42367a5de448ddecf6ee7c09f73580a6b28}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32128PostgreSQL 11 Open Items2018-06-26T23:12:23Z<p>Davidrowley: /* Open Issues */ partition index rename now fixed</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff], awaiting testing<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** 3 possible ways to fix. David has sent different patches for all 3. [https://www.postgresql.org/message-id/CAKJS1f9KG5nnOFhigWm4ND5Ut-yU075iJyA%2BACVyQnZ-ZW1Qtw%40mail.gmail.com 1], [https://www.postgresql.org/message-id/CAKJS1f-OYZZJOr7F6eJQ3WK2cspMp13n%3DQHP5V7Vm0wzKYzaxA%40mail.gmail.com 2] and [https://www.postgresql.org/message-id/CAKJS1f9cqoSKS9JVcBKGa2mdn-24YPWc9XLzFDNsmjJMUpth1w%40mail.gmail.com 3]<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com Server crashed with dense_rank on partition table]<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Introduced by {{PgCommitURL|16828d5c0273b4fe5f10f42588005f16b415b2d8}} (Fast ALTER TABLE ADD COLUMN with a non-NULL default)<br />
** Was this fixed by {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}}? (Allow for pg_upgrade of attributes with missing values) and {{PgCommitURL|123efbccea694626b36ad952086d883fa7469aa9}}? (Mark binary_upgrade_set_missing_value as parallel_unsafe)<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf165-=+Drw3Voim7M5EjHT1zwPF9BQRjLFQzCzYnNZEiQ@mail.gmail.com wrong query result with jit_above_cost=0]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
** Fix in: {{PgCommitURL|f49a80c481f74fa81}}<br />
<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
=== resolved before 11beta2 ===<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
* [https://www.postgresql.org/message-id/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com Performance regression with PostgreSQL 11 and partitioning]<br />
** Fixed in: {{PgCommitURL|7d872c91a3f9d49b56117557cdbb0c3d4c620687}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32127PostgreSQL 11 Open Items2018-06-26T23:11:09Z<p>Davidrowley: /* resolved before 11beta2 */ Partitioning planning regression now fixed.</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff], awaiting testing<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** 3 possible ways to fix. David has sent different patches for all 3. [https://www.postgresql.org/message-id/CAKJS1f9KG5nnOFhigWm4ND5Ut-yU075iJyA%2BACVyQnZ-ZW1Qtw%40mail.gmail.com 1], [https://www.postgresql.org/message-id/CAKJS1f-OYZZJOr7F6eJQ3WK2cspMp13n%3DQHP5V7Vm0wzKYzaxA%40mail.gmail.com 2] and [https://www.postgresql.org/message-id/CAKJS1f9cqoSKS9JVcBKGa2mdn-24YPWc9XLzFDNsmjJMUpth1w%40mail.gmail.com 3]<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com Server crashed with dense_rank on partition table]<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Introduced by {{PgCommitURL|16828d5c0273b4fe5f10f42588005f16b415b2d8}} (Fast ALTER TABLE ADD COLUMN with a non-NULL default)<br />
** Was this fixed by {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}}? (Allow for pg_upgrade of attributes with missing values) and {{PgCommitURL|123efbccea694626b36ad952086d883fa7469aa9}}? (Mark binary_upgrade_set_missing_value as parallel_unsafe)<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A%40mail.gmail.com Error during partition index rename]<br />
** [https://www.postgresql.org/message-id/CAKJS1f_EJhgmxaEneEKszx2ze4Z0y2op9XEswqg659wjjGdNWA%40mail.gmail.com Fixes the reported issue]<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf165-=+Drw3Voim7M5EjHT1zwPF9BQRjLFQzCzYnNZEiQ@mail.gmail.com wrong query result with jit_above_cost=0]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
** Fix in: {{PgCommitURL|f49a80c481f74fa81}}<br />
<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
=== resolved before 11beta2 ===<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
* [https://www.postgresql.org/message-id/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com Performance regression with PostgreSQL 11 and partitioning]<br />
** Fixed in: {{PgCommitURL|7d872c91a3f9d49b56117557cdbb0c3d4c620687}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32126PostgreSQL 11 Open Items2018-06-26T23:09:19Z<p>Davidrowley: /* Open Issues */ Performance regression with partitioning is fixed in 7d872c91a</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff], awaiting testing<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** 3 possible ways to fix. David has sent different patches for all 3. [https://www.postgresql.org/message-id/CAKJS1f9KG5nnOFhigWm4ND5Ut-yU075iJyA%2BACVyQnZ-ZW1Qtw%40mail.gmail.com 1], [https://www.postgresql.org/message-id/CAKJS1f-OYZZJOr7F6eJQ3WK2cspMp13n%3DQHP5V7Vm0wzKYzaxA%40mail.gmail.com 2] and [https://www.postgresql.org/message-id/CAKJS1f9cqoSKS9JVcBKGa2mdn-24YPWc9XLzFDNsmjJMUpth1w%40mail.gmail.com 3]<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com Server crashed with dense_rank on partition table]<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Introduced by {{PgCommitURL|16828d5c0273b4fe5f10f42588005f16b415b2d8}} (Fast ALTER TABLE ADD COLUMN with a non-NULL default)<br />
** Was this fixed by {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}}? (Allow for pg_upgrade of attributes with missing values) and {{PgCommitURL|123efbccea694626b36ad952086d883fa7469aa9}}? (Mark binary_upgrade_set_missing_value as parallel_unsafe)<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A%40mail.gmail.com Error during partition index rename]<br />
** [https://www.postgresql.org/message-id/CAKJS1f_EJhgmxaEneEKszx2ze4Z0y2op9XEswqg659wjjGdNWA%40mail.gmail.com Fixes the reported issue]<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf165-=+Drw3Voim7M5EjHT1zwPF9BQRjLFQzCzYnNZEiQ@mail.gmail.com wrong query result with jit_above_cost=0]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
** Fix in: {{PgCommitURL|f49a80c481f74fa81}}<br />
<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
=== resolved before 11beta2 ===<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowleyhttps://wiki.postgresql.org/index.php?title=PostgreSQL_11_Open_Items&diff=32122PostgreSQL 11 Open Items2018-06-26T13:22:12Z<p>Davidrowley: /* Open Issues */ Listed patches for run-time pruning with UNION ALL bug.</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]<br />
<br />
* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]<br />
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a<br />
<br />
* [https://www.postgresql.org/message-id/2840048a-1184-417a-9da8-3299d207a1d7@postgrespro.ru pg_replication_slot_advance may cause assertion failures with incorrect LSN values]<br />
** Fix committed in [https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=f731cfa94c00164814625d5753d376a4a7c43fff f731cfa94c00164814625d5753d376a4a7c43fff], awaiting testing<br />
<br />
* [https://www.postgresql.org/message-id/d01b31f5-0b3e-b69a-1504-a79649d81f46@iki.fi SCRAM with channel binding downgrade attack]<br />
** [https://www.postgresql.org/message-id/20180517140525.GC546@momjian.us Other thread]<br />
** [https://www.postgresql.org/message-id/20180522082218.GA12027%40paquier.xyz patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYQD1xSM7=XrY6rv2a-W43gKpcTH76F3nSp5o2SGWeCkA@mail.gmail.com Deal with BEFORE ROW triggers in partitioned tables in some way]<br />
<br />
* [https://www.postgresql.org/message-id/87r2m10zm2.fsf%40news-spur.riddles.org.uk Portability concerns over pq_sendbyte?]<br />
<br />
* [https://www.postgresql.org/message-id/94dd7a4b-5e50-0712-911d-2278e055c622@dalibo.com Performance regression with PostgreSQL 11 and partitioning]<br />
<br />
* [https://www.postgresql.org/message-id/HE1PR03MB17068BB27404C90B5B788BCABA7B0@HE1PR03MB1706.eurprd03.prod.outlook.com Runtime partition pruning does not handle UNION ALL parents correctly]<br />
** 3 possible ways to fix. David has sent different patches for all 3. [https://www.postgresql.org/message-id/CAKJS1f9KG5nnOFhigWm4ND5Ut-yU075iJyA%2BACVyQnZ-ZW1Qtw%40mail.gmail.com 1], [https://www.postgresql.org/message-id/CAKJS1f-OYZZJOr7F6eJQ3WK2cspMp13n%3DQHP5V7Vm0wzKYzaxA%40mail.gmail.com 2] and [https://www.postgresql.org/message-id/CAKJS1f9cqoSKS9JVcBKGa2mdn-24YPWc9XLzFDNsmjJMUpth1w%40mail.gmail.com 3]<br />
<br />
* [https://www.postgresql.org/message-id/eb59ce0b-4c95-98a1-1237-a9b300d1a9fe@joeconway.com assert in nested SQL procedure call in current HEAD] [https://www.postgresql.org/message-id/29608.1518533639@sss.pgh.pa.us see also]<br />
<br />
* [https://www.postgresql.org/message-id/CAJ3gD9fRbEzDqdeDq1jxqZUb47kJn%2BtQ7%3DBcgjc8quqKsDViKQ%40mail.gmail.com Concurrency bug in UPDATE of partition-key]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6ktu-8tefLWtQuuZBYFaZA83vUzuRd7c1YHC-yEWyYFpg%40mail.gmail.com Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6kmzWmur5HhA_aU6gYVFu0RLQdgJJ%2BaC9SLdcOvBSrpfA%40mail.gmail.com Server crashed with dense_rank on partition table]<br />
** David Rowley reports that the first bad commit is reported {{PgCommitURL|4b9094eb6e14dfdbed61278ea8e51cc846e43579}} (Adapt to LLVM 7+ Orc API changes.)<br />
** Amit Langote believes based on the core dump that the problem may be in {{PgCommitURL|bf6c614a2f2c58312b3be34a47e7fb7362e07bcb}}) (Do execGrouping.c via expression eval machinery, take two.)<br />
<br />
* [https://www.postgresql.org/message-id/19987.1529420110@sss.pgh.pa.us Fast default feature fails in pg_upgrade]<br />
** Introduced by {{PgCommitURL|16828d5c0273b4fe5f10f42588005f16b415b2d8}} (Fast ALTER TABLE ADD COLUMN with a non-NULL default)<br />
** Was this fixed by {{PgCommitURL|2448adf29c543befbac59f1ecfbb3ef4b0d808ce}}? (Allow for pg_upgrade of attributes with missing values) and {{PgCommitURL|123efbccea694626b36ad952086d883fa7469aa9}}? (Mark binary_upgrade_set_missing_value as parallel_unsafe)<br />
<br />
* [https://www.postgresql.org/message-id/20180626071305.GH31353%40paquier.xyz Non-reserved replication slots and slot advancing]<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6mfYMS3OX0ywjOiWiGSEKhJf-1zdeTceHFbd0mScUzU5A%40mail.gmail.com Error during partition index rename]<br />
** [https://www.postgresql.org/message-id/CAKJS1f_EJhgmxaEneEKszx2ze4Z0y2op9XEswqg659wjjGdNWA%40mail.gmail.com Fixes the reported issue]<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]<br />
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]<br />
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]<br />
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]<br />
<br />
* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
* [https://www.postgresql.org/message-id/152746742177.1291.9847032632907407358%40wrigleys.postgresql.org Default values in partition tables don't work as expected and allow NOT NULL violation]<br />
* [https://www.postgresql.org/message-id/CABOikdPOewjNL%3D05K5CbNMxnNtXnQjhTx2F--4p4ruorCjukbA%40mail.gmail.com PANIC during crash recovery of a recently promoted standby]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]<br />
** Fixed in: {{PgCommitURL|0c8910a0cab7c1e439bf5f5850122c36359e6799}}<br />
* [https://www.postgresql.org/message-id/5AF43E02.30000@lab.ntt.co.jp postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers]<br />
** Fixed in: {{PgCommitURL|7fc7dac1a711d0dbd01d2daf6dc97d27d6c6409c}}<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]<br />
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}<br />
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]<br />
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20180529210212.GE6632%40paquier.xyz Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 11beta3 ===<br />
<br />
=== resolved before 11beta2 ===<br />
* [https://www.postgresql.org/message-id/CAKJS1f8w8+awsxgea8wt7_UX8qzOQ=Tm1LD+U1fHqBAkXxkW2w@mail.gmail.com Needless additional partition check in INSERT]<br />
** Fixed in: {{PgCommitURL|5b0c7e2f75}}<br />
<br />
* [https://postgr.es/m/aeb9c3a7-3c3f-a57f-1a18-c8d4fcdc2a1f@enterprisedb.com pg_resetwal fails with relative path to data dir]<br />
** Bug fix: {{PgCommitURL|1d96c1b91a4b7da6288ee63671a234b557ff5ccf}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/152802081668.26724.16985037679312485972%40wrigleys.postgresql.org Parallel Hash: invalid DSA memory alloc request size 1073741824]<br />
** Bug fix: {{PgCommitURL|86a2218eb00eb6f97898945967c5f9c95c72b4c6}}<br />
<br />
* [https://www.postgresql.org/message-id/20180525052805.GA15634%40paquier.xyz pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced]<br />
** Bug fix: {{PgCommitURL|f731cfa94c00164814625d5753d376a4a7c43fff}}<br />
<br />
* [https://www.postgresql.org/message-id/20180529211559.GF6632%40paquier.xyz pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development]<br />
** Fixed in: {{PgCommitURL|bde64eb6107622e8438dd61b93afd4d1adf178b3}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f94Ojk0og9GMkRHGt8wHTW%3Dijq5KzJKuoBoqWLwSVwGmw%40mail.gmail.com Partitioning with temp tables is broken]<br />
** Fixed in: {{PgCommitURL|1c7c317cd9d1e5647454deed11b55dae764c83bf}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6%3DtPJ6nJ08r__nU_pmLQiC0xY15Fn0HvG1Cprsjdd9s_Q%40mail.gmail.com Server crash during parallel append path generation]<br />
** Fixed in: {{PgCommitURL|403318b71f7058ecbfb65bcc7de1eec96cd35d3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6=q4+Mw8gOOX16ef6ZMFp9Cve7KWFstUsrDa4GiFaXGUQ@mail.gmail.com Partition-wise aggregation asserts out]<br />
** Fixed in: {{PgCommitURL|c6f28af5d7af87d7370e5f169251d91437f100a2}}<br />
<br />
=== resolved before 11beta1 ===<br />
<br />
* [http://postgr.es/m/87sh71cakz.fsf@ars-thinkpad Indexes on partitioned tables and foreign partitions]<br />
** appears to be a bug in 8b08f7d4 (Local partitioned indexes)<br />
** Fixed in: {{PgCommitURL|4eaa53727542c39cca71b80e8ff3e1f742d64452}}<br />
<br />
* [https://www.postgresql.org/message-id/a66879e5-636f-d4dd-b4a4-92bdca5a828f%40lab.ntt.co.jp \d doesn't show partitioned tables' foreign key]<br />
** Fixed in: {{PgCommitURL|93316299d6a185bed0a4be5376508fe2f7e6b2d6}}<br />
<br />
* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]<br />
** Regression caused by commit 8561e48.<br />
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}<br />
<br />
* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]<br />
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}<br />
<br />
* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]<br />
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]<br />
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}<br />
<br />
* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]<br />
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]<br />
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]<br />
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}<br />
<br />
* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]<br />
** coverage report shows it's completely untested, too<br />
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}<br />
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}<br />
<br />
* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]<br />
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}<br />
<br />
* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]<br />
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]<br />
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]<br />
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}<br />
<br />
* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]<br />
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}<br />
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]<br />
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}<br />
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}<br />
<br />
* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]<br />
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}<br />
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]<br />
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]<br />
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}<br />
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]<br />
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}<br />
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}<br />
<br />
* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]<br />
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]<br />
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}<br />
<br />
* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]<br />
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}<br />
<br />
* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]<br />
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]<br />
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}<br />
<br />
* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]<br />
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}<br />
<br />
* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]<br />
<br />
* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]<br />
<br />
* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]<br />
<br />
* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]<br />
<br />
* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]<br />
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}<br />
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]<br />
<br />
* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]<br />
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}<br />
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}<br />
<br />
* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]<br />
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}<br />
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}<br />
<br />
* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]<br />
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}<br />
<br />
* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]<br />
<br />
* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]<br />
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]<br />
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}<br />
<br />
* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]<br />
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}<br />
<br />
* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]<br />
** Bug fix: {{PgCommitURL|d758d9702e2f64f08565e18eb6cb7991efa2dc16}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]<br />
** Bug fix: {{PgCommitURL|bef5fcc36be3d08ec123889a0c82f5e07a63ff88}}<br />
<br />
* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]<br />
** Bug fix: {{PgCommitURL|2efc924180f096070d684a712d6c162b6ae0a5e7}}<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: 8th of April 2018<br />
* beta1: 24th of May 2018<br />
* beta2: 28th of June 2018<br />
* beta3: TBD<br />
<br />
[[Category:Open_Items]]</div>Davidrowley