https://wiki.postgresql.org/api.php?action=feedcontributions&user=Masaofujii&feedformat=atomPostgreSQL wiki - User contributions [en]2024-03-29T05:14:28ZUser contributionsMediaWiki 1.35.13https://wiki.postgresql.org/index.php?title=PgCon_2023_Developer_Meeting&diff=37700PgCon 2023 Developer Meeting2023-03-29T18:05:23Z<p>Masaofujii: /* RSVPs */</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 />
# Masao Fujii<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>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36003PostgreSQL 14 Open Items2021-05-19T03:03:06Z<p>Masaofujii: </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/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Owner: Dean Rasheed<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 />
=== 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 />
=== 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>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=35912PostgreSQL 14 Open Items2021-04-14T03:29:12Z<p>Masaofujii: Add new open item about pg_stat_wal</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 />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US" (BCP47 language tags). Unfortunately the default value chosen by initdb is in the former style (users would have to use something like initdb --lc-collate=en-US for the version reporting to work).<br />
** {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} was committed to tolerate the failure so at least we don't raise an error, but unfortunately we have no version information<br />
** We should either figure out how to improve this situation (translate the names, but how? and when? ask the OS for a default in the BCP47 style? how?), or document the limitation<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Owner: Tomas Vondra<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 />
** Owner: Andrew Dunstan<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Owner: Michael Paquier<br />
** Patch proposed [https://www.postgresql.org/message-id/YHZG3zEpO0PbpeHL%40paquier.xyz here]<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 />
** Owner: Peter Eisentraut<br />
** Proposed patches at [https://www.postgresql.org/message-id/2197698.1617984583%40sss.pgh.pa.us]<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 />
** Owner: Peter Eisentraut<br />
** Patch available at [https://www.postgresql.org/message-id/alpine.DEB.2.22.394.2104071516470.2724014@pseudo]<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Owner: Heikki Linnakangas<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql autoanalyze for partitioned tables should handle ATTACH/DETACH/DROP]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Owner: Bruce Momjian<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Owner: Fujii Masao<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal]<br />
** Owner: Fujii Masao<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/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** With reimplementation of extract to return numeric, this might be an opportune time to fix this one way or the other.<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 />
** since PG13<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<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 />
=== 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 14beta1 ===<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://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: <br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=35911PostgreSQL 14 Open Items2021-04-14T03:26:06Z<p>Masaofujii: Add new open item related to TRUNCATE on foreign tables</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 />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US" (BCP47 language tags). Unfortunately the default value chosen by initdb is in the former style (users would have to use something like initdb --lc-collate=en-US for the version reporting to work).<br />
** {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} was committed to tolerate the failure so at least we don't raise an error, but unfortunately we have no version information<br />
** We should either figure out how to improve this situation (translate the names, but how? and when? ask the OS for a default in the BCP47 style? how?), or document the limitation<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Owner: Tomas Vondra<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 />
** Owner: Andrew Dunstan<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Owner: Michael Paquier<br />
** Patch proposed [https://www.postgresql.org/message-id/YHZG3zEpO0PbpeHL%40paquier.xyz here]<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 />
** Owner: Peter Eisentraut<br />
** Proposed patches at [https://www.postgresql.org/message-id/2197698.1617984583%40sss.pgh.pa.us]<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 />
** Owner: Peter Eisentraut<br />
** Patch available at [https://www.postgresql.org/message-id/alpine.DEB.2.22.394.2104071516470.2724014@pseudo]<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Owner: Heikki Linnakangas<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql autoanalyze for partitioned tables should handle ATTACH/DETACH/DROP]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Owner: Bruce Momjian<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Owner: Alvaro Herrera<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Owner: Fujii Masao<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/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** With reimplementation of extract to return numeric, this might be an opportune time to fix this one way or the other.<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 />
** since PG13<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<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 />
=== 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 14beta1 ===<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://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: <br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=35739PostgreSQL 14 Open Items2021-02-22T09:32:11Z<p>Masaofujii: Fixed "Atomic initialization of waitStart done at backend startup" issue.</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/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Owner: Thomas Munro<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Owner: Michael Paquier<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/flat/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<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 />
=== 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 />
** Owner: Michael Paquier<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta1 ===<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 />
** Owner: Fujii Masao<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
== Won't Fix ==<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: <br />
* Beta 1: <br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=35232PostgreSQL 13 Open Items2020-08-21T12:01:48Z<p>Masaofujii: Mark "explain(format text) showing buffers during planning" 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 13beta4 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAOBaU_aQLnaDs4q%3DijVPWocWe5vv82VOU0Ypc%2B6WuVTwi%2Bcb1w%40mail.gmail.com#8465918b43988cbda101697cbd1cf8db explain(format text) showing buffers during planning]<br />
** Original commit: {{PgCommitURL|ce77abe63cfc85fb0bc236deb2cc34ae35cb5324}}<br />
** Owner: Fujii Masao<br />
** Fixed at: {{PgCommitURL|9d701e624f4b9386cbd99519dab7936afe3d5aed}}<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 />
* Beta 4: TBD<br />
<br />
[[Category:Open_Items]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=34112PostgreSQL 12 Open Items2019-09-25T16:22:56Z<p>Masaofujii: Add recovery 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/flat/5CF28EA0.80902%40anastigmatix.net Should we change jsonpath to avoid using standard syntax for not-quite-standard features?]<br />
** Additional discussion [https://www.postgresql.org/message-id/flat/CAPpHfdvDci4iqNF9fhRkTqhe-5_8HmzeLt56drH%2B_Rv2rNRqfg%40mail.gmail.com here]<br />
* [https://www.postgresql.org/message-id/CAHGQGwEYYg_Ng+03FtZczacCpYgJ2Pn=B_wPtWF+FFLYDgpa1g@mail.gmail.com After recovery starting when backup_label exists, but not recovery.signal shuts down, the restarted recovery doesn't enter an archive recovery mode and may fail.]<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/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi B-Tree Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** This was fixed in the new GiST page deletion by {{PgCommitURL|6655a7299d835dea9e8e0ba69cc5284611b96f29}}, but the same issue remains in B-tree.<br />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6nZiO9-eEpr1ZD84bT1mBoVmeZkfont8iSpcmYrjhGWgA@mail.gmail.com getting ERROR "relation 16401 has no triggers" with partition foreign key alter]<br />
** Fixed in: {{PgCommitURL|5562272a4229cfa57354aa203cffd36b4e7f70cb}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzmj6pz98qZ6%2BRo-%3DtHvyBJ6q0yxHV8QLOr6O0mE20Nw9Q%40mail.gmail.com pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)]<br />
** Fixed in: {{PgCommitURL|d004147eb3ece6b5981dbdd3d918ffc3f23fc505}}<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 />
* [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 />
** Fixed in {{PgCommitURL|14ef15a22246ca17c949e7a9d1abe14c8874d743}}<br />
* [https://www.postgresql.org/message-id/20190730211759.zqzt7xfchvmuja4i@development Change semantics of log_statement_sample_rate?]<br />
** Fixed in {{PgCommitURL|75506195da81d75597a4025b72f8367e6c45f60d}}<br />
* [https://www.postgresql.org/message-id/flat/CAK%3D1%3DWrek44Ese1V7LjKiQS-Nd-5LgLi_5_CskGbpggKEf3tKQ%40mail.gmail.com REL_12_STABLE crashing with assertion failure in ExtractReplicaIdentity]<br />
** The report mentions REL_12_STABLE, but it's a pre-existing issue just made visible by new checks. Nonetheless, it's not clear that there are real consequences beyond the assertion failure, so no change in prior branches.<br />
** Fixed in {{PgCommitURL|f63a5ead9d04467e1c1847bd5e3d87c4dca6cd35}}<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 12rc1 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/TY2PR01MB2443EC8286995378AEB7D9F8F5B10%40TY2PR01MB2443.jpnprd01.prod.outlook.com ECPG DECLARE STATEMENT definitional and quality-of-implementation concerns]<br />
** Reverted by {{PgCommitURL|96b6c82c9dd4a6a91c7e54bf42d36da111959ec6}}<br />
* [https://www.postgresql.org/message-id/flat/48ee4c56-e1df-b39d-2cad-c7d80b120eb5%402ndquadrant.com ecpglib major version change]<br />
** Reverted by {{PgCommitURL|fbd1cb2fd9796a08a198d929774280ecce933057}}<br />
* [https://www.postgresql.org/message-id/31481.1568303470@sss.pgh.pa.us Leakproofness of texteq()/textne()]<br />
** Fixed in {{PgCommitURL|c160b8928c77cb52f52d7509465b6c7d8026bd27}}<br />
* [https://www.postgresql.org/message-id/22566.1568675619@sss.pgh.pa.us Nondeterministic collations break text_pattern_ops]<br />
** Fixed in {{PgCommitURL|2810396312664bdb941e549df7dfa75218d73a1c}}<br />
<br />
=== resolved before 12beta4 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHU7rYZo_C4ULsAx_LAj8az9zqgrD8WDd4hTegDTMM1LMqrBsg@mail.gmail.com EvalPlanQual crash due to wrong slot tupdesc]<br />
** Commit {{PgCommitURL|ad0bda5d24ea2bcc72b5e50020e3c79bab10836b}} Author: Andres Freund<br />
** Fixed in {{PgCommitURL|27cc7cd2bc8a5e8efc8279bc5d2a8ae42fd8ad33}}<br />
* [https://www.postgresql.org/message-id/15977-f4eb49ebdcacc65b@postgresql.org BUG #15977: Inconsistent behavior in chained transactions]<br />
** behavior of AND CHAIN on implicit transactions is not consistent<br />
** Commit {{PgCommitURL|280a408b48d5ee42969f981bceb9e9426c3a344c}} Author: Peter Eisentraut<br />
** [https://commitfest.postgresql.org/24/2265/ fix ready], consisting in disabling chaining when in an implicit transaction<br />
** Fixed in {{PgCommitURL|862ef372d6b23629f93d4afc123ddd7d172501ac}}<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
** Proposed patch is in thread [https://www.postgresql.org/message-id/4859321552643736@myt5-02b80404fd9e.qloud-c.yandex.net Change ereport level for QueuePartitionConstraintValidation]<br />
** Fixed in {{PgCommitURL|db438318997b75f4b40c61258da56384039fa43f}}<br />
* [https://postgr.es/m/20190816200048.GA5514@alvherre.pgsql Images in documentation don't work in VPATH]<br />
** Fixed in {{PgCommitURL|842ac79407a136}}<br />
* [https://www.postgresql.org/message-id/d6ffbebb-a0d2-181c-811d-b029b2225ed7@iki.fi default_table_access_method is not in sample config file]<br />
** {{PgCommitURL|f7db0ac7d5b6ba9728616a1cc36288cb4f817e66}}<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 />
** Code fix committed at {{PgCommitURL|f1bf619acdff15b88b5729f8de6df4eed609b3a0}}<br />
** Doc fix committed at {{PgCommitURL|45aaaa42fefad6e2f164647e373346a5a4123dad}}<br />
<br />
=== resolved before 12beta3 ===<br />
<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 />
** Fixed in: {{PgCommitURL|2abd7ae9b20bcd810d4f19d28aefb97048813825}}<br />
* [https://www.postgresql.org/message-id/CAE9k0PmNaMD2oHTEAhRyxnxpaDaYkuBYkLa1dpOpn=RS0iS2AQ@mail.gmail.com Wrong-slot-type assertion failure]<br />
** Commit {{PgCommitURL|15d8f83128e15de97de61430d0b9569f5ebecc26}} Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|af3deff3f2ac79585481181cb198b04c67486c09}}<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 />
** Fixed in: {{PgCommitURL|ecbdd009344d3a00733e4382f50137b5e0248ce8}}<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 />
** Fixed in: {{PgCommitURL|e3899ffd8beafdaaa037b503163a9f572e9fc729}}<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 />
* [https://www.postgresql.org/message-id/8736jdhbhc.fsf@ansel.ydns.eu Crash in mcv_get_match_bitmap with sqlsmith]<br />
** Fixed in: {{PgCommitURL|e8b6ae2130e3a95bb776708a9a7c9cb21fe8ac87}}<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 />
** Fixed in: {{PgCommitURL|6655a7299d835dea9e8e0ba69cc5284611b96f29}}<br />
* [https://www.postgresql.org/message-id/CA+u7OA5Hp0ra235F3czPom_FyAd-3+XwSJmX95r1+sRPOJc9VQ@mail.gmail.com REINDEX CONCURRENTLY causes ALTER TABLE to fail]<br />
** Fixed in: {{PgCommitURL|28bbf7a81b3a30504cc7dfdbd76b410d1f127b8e}}<br />
* [https://www.postgresql.org/message-id/20190801184333.GA21369@alvherre.pgsql Progress reporting of REINDEX, CREATE TABLE and CLUSTER ignore each other]<br />
** A progress may be started while another one is already in progress. Hence, if progress gets stopped the previously-started state is removed, causing all follow-up updates to not happen.<br />
** Progress updates happening in a code path shared between those three commands may clobber a previous state present. <br />
** Fixed in: {{PgCommitURL|da47e43dc32e3c5916396f0cbcfa974b371e4875}}<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 />
== Won't Fix ==<br />
<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 />
** A proposed patch exists, but some feel that cure is worse than the disease, so we may end up doing nothing 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: Aug. 8, 2019<br />
* beta4: Sep. 12, 2019<br />
* rc1: Sep. 26, 2019<br />
* GA: Oct. 3, 2019<br />
<br />
[[Category:Open_Items]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33422PostgreSQL 12 Open Items2019-05-07T17:25:00Z<p>Masaofujii: Resolved the open item; Add TRUNCATE option to VACUUM.</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/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/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/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robest Haas<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 />
* [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/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<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 />
<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/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<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/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Bug appears fixed as of {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
** Unfortunately, test cases show intermittent deadlocks, which we can't realistically fix now, so test cases will have to come out<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 />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<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 />
<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>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29970PostgreSQL 10 Open Items2017-04-25T16:12:29Z<p>Masaofujii: Fixed "priority in quorum-based sync rep" issue</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
* pg_dump and partitioned tables<br />
** {{messageLink|20170409235057.GA2842536@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
** original commit: {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Stephen Frost, [http://postgr.es/m/20170413150540.GQ9812@tamriel.snowman.net previously Robert Haas])<br />
* [https://www.postgresql.org/message-id/4b498969-fd37-9c3d-3981-389507515cc6%40lab.ntt.co.jp UPDATE/DELETE statement-level triggers don't fire on partitioned tables]<br />
** Patch exists<br />
* [https://www.postgresql.org/message-id/8f6f6519-a807-7bf1-acf7-f045da4ce385%40lab.ntt.co.jp Dropping a partitioned table takes too long]<br />
** Patch exists<br />
<br />
=== Logical Replication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|665d1fa}} (principal author: Petr Jelinek; owner: Peter Eisentraut)<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs]<br />
** owner: Andres Freund {{messageLink|20170413045812.GA2917375@tornado.leadboat.com|notified}}<br />
** none of the issues are v10 specific but they affect logical replication feature usability<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170416060841.GH2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com tablesync patch broke the assumption that logical rep depends on?]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170413045605.GD2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEsttg9P9LOOavoc9d6VB1zVmYgfBk=Ljsk-UL9cEf-eA@mail.gmail.com logical replication and PANIC during shutdown checkpoint in publisher]<br />
** Also affects v9.4-v9.6 but v10 can trigger it from more places<br />
** {{messageLink|20170416061258.GI2870454@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqTHQJ7zODLCLmhg9oz03qow6eh27NhEqzT+CT64eku5Ug@mail.gmail.com Patch exists] to block properly WAL generation at shutdown in WAL senders.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwFDWh_Qr-q_GEMpD+qH=vYPMdVqw=ZOSY3kX_Pna9R9SA@mail.gmail.com some review comments on logical rep code]<br />
** {{messageLink|20170416061449.GJ2870454@tornado.leadboat.com|notified}}<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
** {{messageLink|20170410035323.GA2846583@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqSbsCBCxy8-DtwzRxYgTnbGUtY4uFEkLQhG%3DR%3Duo%3Dg8Fw%40mail.gmail.com patch exists]<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/CAKOSWN=hUQWwyCJS8a3gTTUkvMkeg2iwSCCs=df0OYxJ_6H0kA@mail.gmail.com Removing ADD GENERATED for identity columns]<br />
** original commit: {{PgCommitURL|3217327}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170414055644.GF2870454@tornado.leadboat.com|notified}})<br />
** Patch exists.<br />
<br />
* [https://www.postgresql.org/message-id/D992B4C2-8F80-4DE0-8348-6E0696C3F967@citusdata.com ALTER SEQUENCE RESTART is not consurrent-safe]<br />
** original commit: {{PgCommitURL|1753b1b}} (owner: Peter Eisentraut)<br />
** [https://www.postgresql.org/message-id/CAB7nPqRev_wK4k39hQBpQZRQ17v29guxfobnnmTYT_-hUU67BA@mail.gmail.com patch exists]<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
* [https://www.postgresql.org/message-id/4905.1492813727@sss.pgh.pa.us parallel query locks up if worker process fails to launch]<br />
** code is broken since birth, but do we really want to ship v10 like this?<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** include partitions in information_schema.tables, pg_tables, and psql's \d listing, etc?<br />
** firm support for status quo, lack of firm support for alternatives<br />
<br />
* [https://www.postgresql.org/message-id/071086d7-6462-f0e7-54ca-b633062e317c%40lab.ntt.co.jp Document that foreign table's partition constraint is not enforced locally]<br />
** Patch exists<br />
** documentation is correct, but this would add emphasis to a point<br />
<br />
* [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** owner [https://www.postgresql.org/message-id/20170412225855.oklyfkbwj2dmbrpu@alap3.anarazel.de proposes] classifying this as a non-bug<br />
** Commit e240a65c7dfc5ad80ab757ecb1aa9b9032c7f8ae improved error reporting<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zMLnH_i1-PVQ-biZzvNx7VcuatriquEnh7HNk6K8Ss3Q@mail.gmail.com PANIC in pg_commit_ts slru after crashes, 2PC restore code at fault]<br />
** Fixed by commit aa203e76004daaee3d70b19cc727ed17b87b3d3a<br />
** Fixed by commit ee01f7092fb6430ad9bb9bb1f42f19d22bcb9329<br />
<br />
* [https://www.postgresql.org/message-id/8a1d4662-9665-59d5-518d-45616b75f06a%40lab.ntt.co.jp COMMENT ON COLUMN fails for partitioned tables]<br />
** Fixed by commit 51175f3638524231405e674e40bde159b0b76727<br />
<br />
* [http://postgr.es/m/CAKJS1f-BmGo410bh5RSPZUvOO0LhmHL2NYmdrC_Jm8pk_FfyCA@mail.gmail.com Allowing extended stats on foreign and partitioned tables]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170414055310.GE2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8c5cdb7f4f6e1d6a6104cb58ce4f23453891651b<br />
<br />
* [https://www.postgresql.org/message-id/12642.1491513976@sss.pgh.pa.us Partitioning optimization broke ConvertRowtypeExpr]<br />
** Fixed by commit 3f902354b08ac788600f0ae54fcbfc1d4e3ea765.<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** Fixed by commit 6f1b9aaae35bfabe2654a8e44ce226c91e7d8bd9<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
** Fixed by commit b2ff37d43cc81348fd8e9d9c5fcc9dfadf790763<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
** Fixed by commit 5a5931533edd2b70bde1f069609f58998dd26fef<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
** Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
** Fixed by commit 5c4488478b182983f290a61fc8cf2ec83548622b<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Fixed by commit 0ef26bb394abedb2745bd838c26ecb3131682bda<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** original commit: {{PgCommitURL|f1b4c77}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235426.GB2842536@tornado.leadboat.com|notified}})<br />
** Fixed by commit c0a8ae7be392aa09dd7e148ff662013e8e148893<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** Fixed by commit 521fd4795e3ec3d0b263b62e5eb58e1557be9c86<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
** Fixed by commit 26ad194cb0a6b955e155d44fb52a74212ce85759<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
** Fixed by commit 3820c63da8d0e59e2bd4476e91968f03be5dd041<br />
<br />
* [http://postgr.es/m/CAMkU=1zrQaPwBN+NcBd3pWCb=vWaiL=mmWfJjDJjh-a7eVr-Og@mail.gmail.com pgbench --progress-timestamp no longer works correctly]<br />
** original commit: {{PgCommitURL|1d63f7d}} (principal author: Tom Lane; owner: Tom Lane {{messageLink|20170411042352.GA2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit feffa0e0795a5a99324890a6dd548ba162ec104c<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235729.GA2842636@tornado.leadboat.com|notified}})<br />
** Fixed by commit 258cef12540fa1cb244881a0f019cefd698c809e<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** original commit: {{PgCommitURL|f35742c}} (principal author: Dilip Kumar; owner: Robert Haas {{messageLink|20170410031734.GB2845039@tornado.leadboat.com|notified}})<br />
** Fixed by commit 4c3b59abf4c476843bca23de7fb66d647627f30e<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
** original commit: {{PgCommitURL|b460f5d}} (principal author: Julien Rouhaud; owner: Robert Haas {{messageLink|20170410031836.GC2845004@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8ff518699f19dd0a5076f5090bac8400b8233f7f<br />
** See also commit 6599c9ac3340b6cd3d86a0a7f866b80a009fecab which attempts to catch other problems of this sort<br />
<br />
* [https://www.postgresql.org/message-id/52d9c443-ec78-5c8a-7a77-0f34aad12b82%40lab.ntt.co.jp RENAME RULE doesn't work with partitioned tables]<br />
** Fixed by commit 02af7857e5694b13c21401d1982ac21d31e27dee<br />
<br />
* [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
** {{messageLink|CA+TgmobTJnasxpRkJxGcHaz85LyqdXBKZRxP6pCCS-UkhcHUBQ@mail.gmail.com|feature request, not bug}}<br />
** implemented in {{PgCommitURL|25542d77dd549940468d1a932809feb9959d717d}}<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** withdrawn<br />
<br />
* [https://www.postgresql.org/message-id/CA%2BTgmobYfFRtcXv1aoXD18%2BRkPU%3Duw39Ajqm1HWyh7V_8QYZ%3DA%40mail.gmail.com pgstathashindex() to handle unused pages in hash index]<br />
** original commit: {{PgCommitURL|e759854}} (principal author: Ashutosh Sharma; owner: Robert Haas {{messageLink|20170412062802.GB2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 9cc27566c1a8d659c15b9eea2413dcc07a7a42c9<br />
<br />
* [https://www.postgresql.org/message-id/30972.1491937807@sss.pgh.pa.us Mishandling of non-parallel-safe initplans/subplans in a parallelized query]<br />
** original commit: {{PgCommitURL|5e6d8d2bb}}<br />
** Fixed by commit 16ebab68862bb5d3595b8c8df083f650d9d7cd20<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** fixed by commits c31671f9b5f6eee9b6726baad2db1795c94839d1, a9254e675bde7dc2d976d207450c559d914c0dd6<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/E1cwSWo-0001hG-Rq@gemulon.postgresql.org Add overview of SCRAM to the FE/BE protocol documentation]. Mention that SASLprep is used on all passwords, UTF-8 or not.<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** fixed by commit 887227a1cc861d87ca0f175cf8bd1447554090eb<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
** fixed by commit 139eb9673cb84c76f493af7e68301ae204199746<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** fixed in pgweb<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** fixed by commit 419a23b478ae760b797188341ddce5b41322684b<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}}<br />
** fixed by commit bf2a691e02d7766f185d9d8e0f092222a5c0a129<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Parallel Query + EXEC_BACKEND + ASLR is broken]<br />
** Problem in 9.6 and later<br />
** Fixed by commits 0ef26bb39 + 32470825d + a74740fbd<br />
<br />
* [https://www.postgresql.org/message-id/CAHE3wgj+2YpFyrg7SAV=-oqTpP2AggT-nRKbR3nkDAt0TA2V6A@mail.gmail.com Different table schema in logical replication crashes]<br />
** fixed by commit e6242c18a5bb08788e6c4cc773952fc8e2a6291a<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** fixed by commit c727f120ff50f624a1ee3abe700d995c18314a0b<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
* [https://www.postgresql.org/message-id/7064.1492022469@sss.pgh.pa.us Inadequate parallel-safety check for SubPlans]<br />
** original commit: {{PgCommitURL|5e6d8d2}} (principal author: Amit Kapila; owner: Robert Haas {{messageLink|20170416061825.GK2870454@tornado.leadboat.com|notified}})<br />
** fixed by commit 39151781c8cd2c8bf6057496426fb9c07178eda5<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqQP-+zbgMiDgFwtoUnQfBV9y86GABuKeEV21PQ_EZDC3A@mail.gmail.com CREATE/DROP SUBSCRIPTION, query cancellations and slot handling]<br />
** fixed by commit dcb39c3<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
** Not a bug. Consensus against current design; no consensus on which replacement to adopt. Need to resolve that debate.<br />
** Fixed by commit 346199dcab4cfb2c023373fb3d859583b59810d7<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7th<br />
* beta1: wrap May 15th, announce May 18th<br />
<br />
References:<br />
* [https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All original schedule]<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZNLxizOkPy4WKdxwKo40Hz96v5jZ%3D07aLe93JW2dZmRA%40mail.gmail.com feature freeze moved]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29915PostgreSQL 10 Open Items2017-04-18T18:11:57Z<p>Masaofujii: Move pg_stat_replication.sync_priority open item to "Design Decisions to Recheck Mid-Beta"</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
* pg_dump and partitioned tables<br />
** {{messageLink|20170409235057.GA2842536@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
** original commit: {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Stephen Frost, [http://postgr.es/m/20170413150540.GQ9812@tamriel.snowman.net previously Robert Haas])<br />
<br />
=== Logical Replication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|665d1fa}} (principal author: Petr Jelinek; owner: Peter Eisentraut)<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs]<br />
** owner: Andres Freund {{messageLink|20170413045812.GA2917375@tornado.leadboat.com|notified}}<br />
** some issues go back to 9.4; some are new in v10<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170416060841.GH2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com tablesync patch broke the assumption that logical rep depends on?]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170413045605.GD2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEsttg9P9LOOavoc9d6VB1zVmYgfBk=Ljsk-UL9cEf-eA@mail.gmail.com logical replication and PANIC during shutdown checkpoint in publisher]<br />
** {{messageLink|20170416061258.GI2870454@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwFDWh_Qr-q_GEMpD+qH=vYPMdVqw=ZOSY3kX_Pna9R9SA@mail.gmail.com some review comments on logical rep code]<br />
** {{messageLink|20170416061449.GJ2870454@tornado.leadboat.com|notified}}<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
** {{messageLink|20170410035323.GA2846583@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqSbsCBCxy8-DtwzRxYgTnbGUtY4uFEkLQhG%3DR%3Duo%3Dg8Fw%40mail.gmail.com patch exists]<br />
<br />
=== Other ===<br />
<br />
* [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** owner [https://www.postgresql.org/message-id/20170412225855.oklyfkbwj2dmbrpu@alap3.anarazel.de proposes] classifying this as a non-bug<br />
<br />
* [https://www.postgresql.org/message-id/7064.1492022469@sss.pgh.pa.us Inadequate parallel-safety check for SubPlans]<br />
** original commit: {{PgCommitURL|5e6d8d2}} (principal author: Amit Kapila; owner: Robert Haas {{messageLink|20170416061825.GK2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAKOSWN=hUQWwyCJS8a3gTTUkvMkeg2iwSCCs=df0OYxJ_6H0kA@mail.gmail.com Removing ADD GENERATED for identity columns]<br />
** original commit: {{PgCommitURL|3217327}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170414055644.GF2870454@tornado.leadboat.com|notified}})<br />
** Patch exists.<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
** This is not a bug. There are some proposals for better design of priority column in pg_stat_replication, but we've not reached the consensus yet. It's better to move this open item to "Design Decisions to Recheck Mid-Beta" section so that we can hear more opinions.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** include partitions in information_schema.tables, pg_tables, and psql's \d listing, etc?<br />
** firm support for status quo, lack of firm support for alternatives<br />
<br />
* [https://www.postgresql.org/message-id/071086d7-6462-f0e7-54ca-b633062e317c%40lab.ntt.co.jp Document that foreign table's partition constraint is not enforced locally]<br />
** Patch exists<br />
** documentation is correct, but this would add emphasis to a point<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zMLnH_i1-PVQ-biZzvNx7VcuatriquEnh7HNk6K8Ss3Q@mail.gmail.com PANIC in pg_commit_ts slru after crashes, 2PC restore code at fault]<br />
** Fixed by commit aa203e76004daaee3d70b19cc727ed17b87b3d3a<br />
** Fixed by commit ee01f7092fb6430ad9bb9bb1f42f19d22bcb9329<br />
<br />
* [https://www.postgresql.org/message-id/8a1d4662-9665-59d5-518d-45616b75f06a%40lab.ntt.co.jp COMMENT ON COLUMN fails for partitioned tables]<br />
** Fixed by commit 51175f3638524231405e674e40bde159b0b76727<br />
<br />
* [http://postgr.es/m/CAKJS1f-BmGo410bh5RSPZUvOO0LhmHL2NYmdrC_Jm8pk_FfyCA@mail.gmail.com Allowing extended stats on foreign and partitioned tables]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170414055310.GE2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8c5cdb7f4f6e1d6a6104cb58ce4f23453891651b<br />
<br />
* [https://www.postgresql.org/message-id/12642.1491513976@sss.pgh.pa.us Partitioning optimization broke ConvertRowtypeExpr]<br />
** Fixed by commit 3f902354b08ac788600f0ae54fcbfc1d4e3ea765.<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** Fixed by commit 6f1b9aaae35bfabe2654a8e44ce226c91e7d8bd9<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
** Fixed by commit b2ff37d43cc81348fd8e9d9c5fcc9dfadf790763<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
** Fixed by commit 5a5931533edd2b70bde1f069609f58998dd26fef<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
** Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
** Fixed by commit 5c4488478b182983f290a61fc8cf2ec83548622b<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Fixed by commit 0ef26bb394abedb2745bd838c26ecb3131682bda<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** original commit: {{PgCommitURL|f1b4c77}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235426.GB2842536@tornado.leadboat.com|notified}})<br />
** Fixed by commit c0a8ae7be392aa09dd7e148ff662013e8e148893<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** Fixed by commit 521fd4795e3ec3d0b263b62e5eb58e1557be9c86<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
** Fixed by commit 26ad194cb0a6b955e155d44fb52a74212ce85759<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
** Fixed by commit 3820c63da8d0e59e2bd4476e91968f03be5dd041<br />
<br />
* [http://postgr.es/m/CAMkU=1zrQaPwBN+NcBd3pWCb=vWaiL=mmWfJjDJjh-a7eVr-Og@mail.gmail.com pgbench --progress-timestamp no longer works correctly]<br />
** original commit: {{PgCommitURL|1d63f7d}} (principal author: Tom Lane; owner: Tom Lane {{messageLink|20170411042352.GA2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit feffa0e0795a5a99324890a6dd548ba162ec104c<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235729.GA2842636@tornado.leadboat.com|notified}})<br />
** Fixed by commit 258cef12540fa1cb244881a0f019cefd698c809e<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** original commit: {{PgCommitURL|f35742c}} (principal author: Dilip Kumar; owner: Robert Haas {{messageLink|20170410031734.GB2845039@tornado.leadboat.com|notified}})<br />
** Fixed by commit 4c3b59abf4c476843bca23de7fb66d647627f30e<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
** original commit: {{PgCommitURL|b460f5d}} (principal author: Julien Rouhaud; owner: Robert Haas {{messageLink|20170410031836.GC2845004@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8ff518699f19dd0a5076f5090bac8400b8233f7f<br />
** See also commit 6599c9ac3340b6cd3d86a0a7f866b80a009fecab which attempts to catch other problems of this sort<br />
<br />
* [https://www.postgresql.org/message-id/52d9c443-ec78-5c8a-7a77-0f34aad12b82%40lab.ntt.co.jp RENAME RULE doesn't work with partitioned tables]<br />
** Fixed by commit 02af7857e5694b13c21401d1982ac21d31e27dee<br />
<br />
* [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
** {{messageLink|CA+TgmobTJnasxpRkJxGcHaz85LyqdXBKZRxP6pCCS-UkhcHUBQ@mail.gmail.com|feature request, not bug}}<br />
** implemented in {{PgCommitURL|25542d77dd549940468d1a932809feb9959d717d}}<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** withdrawn<br />
<br />
* [https://www.postgresql.org/message-id/CA%2BTgmobYfFRtcXv1aoXD18%2BRkPU%3Duw39Ajqm1HWyh7V_8QYZ%3DA%40mail.gmail.com pgstathashindex() to handle unused pages in hash index]<br />
** original commit: {{PgCommitURL|e759854}} (principal author: Ashutosh Sharma; owner: Robert Haas {{messageLink|20170412062802.GB2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 9cc27566c1a8d659c15b9eea2413dcc07a7a42c9<br />
<br />
* [https://www.postgresql.org/message-id/30972.1491937807@sss.pgh.pa.us Mishandling of non-parallel-safe initplans/subplans in a parallelized query]<br />
** original commit: {{PgCommitURL|5e6d8d2bb}}<br />
** Fixed by commit 16ebab68862bb5d3595b8c8df083f650d9d7cd20<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** fixed by commits c31671f9b5f6eee9b6726baad2db1795c94839d1, a9254e675bde7dc2d976d207450c559d914c0dd6<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/E1cwSWo-0001hG-Rq@gemulon.postgresql.org Add overview of SCRAM to the FE/BE protocol documentation]. Mention that SASLprep is used on all passwords, UTF-8 or not.<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** fixed by commit 887227a1cc861d87ca0f175cf8bd1447554090eb<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
** fixed by commit 139eb9673cb84c76f493af7e68301ae204199746<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** fixed in pgweb<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** fixed by commit 419a23b478ae760b797188341ddce5b41322684b<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}}<br />
** fixed by commit bf2a691e02d7766f185d9d8e0f092222a5c0a129<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Parallel Query + EXEC_BACKEND + ASLR is broken]<br />
** Problem in 9.6 and later<br />
** Fixed by commits 0ef26bb39 + 32470825d + a74740fbd<br />
<br />
* [https://www.postgresql.org/message-id/CAHE3wgj+2YpFyrg7SAV=-oqTpP2AggT-nRKbR3nkDAt0TA2V6A@mail.gmail.com Different table schema in logical replication crashes]<br />
** fixed by commit e6242c18a5bb08788e6c4cc773952fc8e2a6291a<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** fixed by commit c727f120ff50f624a1ee3abe700d995c18314a0b<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7th<br />
* beta1: wrap May 15th, announce May 18th<br />
<br />
References:<br />
* [https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All original schedule]<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZNLxizOkPy4WKdxwKo40Hz96v5jZ%3D07aLe93JW2dZmRA%40mail.gmail.com feature freeze moved]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29914PostgreSQL 10 Open Items2017-04-18T18:07:19Z<p>Masaofujii: Fixed "doc improvement for quorum syncrep" open item.</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
* pg_dump and partitioned tables<br />
** {{messageLink|20170409235057.GA2842536@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
** original commit: {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Stephen Frost, [http://postgr.es/m/20170413150540.GQ9812@tamriel.snowman.net previously Robert Haas])<br />
<br />
=== Logical Replication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|665d1fa}} (principal author: Petr Jelinek; owner: Peter Eisentraut)<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs]<br />
** owner: Andres Freund {{messageLink|20170413045812.GA2917375@tornado.leadboat.com|notified}}<br />
** some issues go back to 9.4; some are new in v10<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170416060841.GH2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com tablesync patch broke the assumption that logical rep depends on?]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170413045605.GD2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEsttg9P9LOOavoc9d6VB1zVmYgfBk=Ljsk-UL9cEf-eA@mail.gmail.com logical replication and PANIC during shutdown checkpoint in publisher]<br />
** {{messageLink|20170416061258.GI2870454@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwFDWh_Qr-q_GEMpD+qH=vYPMdVqw=ZOSY3kX_Pna9R9SA@mail.gmail.com some review comments on logical rep code]<br />
** {{messageLink|20170416061449.GJ2870454@tornado.leadboat.com|notified}}<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
** {{messageLink|20170410035323.GA2846583@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqSbsCBCxy8-DtwzRxYgTnbGUtY4uFEkLQhG%3DR%3Duo%3Dg8Fw%40mail.gmail.com patch exists]<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
<br />
* [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** owner [https://www.postgresql.org/message-id/20170412225855.oklyfkbwj2dmbrpu@alap3.anarazel.de proposes] classifying this as a non-bug<br />
<br />
* [https://www.postgresql.org/message-id/7064.1492022469@sss.pgh.pa.us Inadequate parallel-safety check for SubPlans]<br />
** original commit: {{PgCommitURL|5e6d8d2}} (principal author: Amit Kapila; owner: Robert Haas {{messageLink|20170416061825.GK2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAKOSWN=hUQWwyCJS8a3gTTUkvMkeg2iwSCCs=df0OYxJ_6H0kA@mail.gmail.com Removing ADD GENERATED for identity columns]<br />
** original commit: {{PgCommitURL|3217327}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170414055644.GF2870454@tornado.leadboat.com|notified}})<br />
** Patch exists.<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** include partitions in information_schema.tables, pg_tables, and psql's \d listing, etc?<br />
** firm support for status quo, lack of firm support for alternatives<br />
<br />
* [https://www.postgresql.org/message-id/071086d7-6462-f0e7-54ca-b633062e317c%40lab.ntt.co.jp Document that foreign table's partition constraint is not enforced locally]<br />
** Patch exists<br />
** documentation is correct, but this would add emphasis to a point<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zMLnH_i1-PVQ-biZzvNx7VcuatriquEnh7HNk6K8Ss3Q@mail.gmail.com PANIC in pg_commit_ts slru after crashes, 2PC restore code at fault]<br />
** Fixed by commit aa203e76004daaee3d70b19cc727ed17b87b3d3a<br />
** Fixed by commit ee01f7092fb6430ad9bb9bb1f42f19d22bcb9329<br />
<br />
* [https://www.postgresql.org/message-id/8a1d4662-9665-59d5-518d-45616b75f06a%40lab.ntt.co.jp COMMENT ON COLUMN fails for partitioned tables]<br />
** Fixed by commit 51175f3638524231405e674e40bde159b0b76727<br />
<br />
* [http://postgr.es/m/CAKJS1f-BmGo410bh5RSPZUvOO0LhmHL2NYmdrC_Jm8pk_FfyCA@mail.gmail.com Allowing extended stats on foreign and partitioned tables]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170414055310.GE2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8c5cdb7f4f6e1d6a6104cb58ce4f23453891651b<br />
<br />
* [https://www.postgresql.org/message-id/12642.1491513976@sss.pgh.pa.us Partitioning optimization broke ConvertRowtypeExpr]<br />
** Fixed by commit 3f902354b08ac788600f0ae54fcbfc1d4e3ea765.<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** Fixed by commit 6f1b9aaae35bfabe2654a8e44ce226c91e7d8bd9<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
** Fixed by commit b2ff37d43cc81348fd8e9d9c5fcc9dfadf790763<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
** Fixed by commit 5a5931533edd2b70bde1f069609f58998dd26fef<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
** Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
** Fixed by commit 5c4488478b182983f290a61fc8cf2ec83548622b<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Fixed by commit 0ef26bb394abedb2745bd838c26ecb3131682bda<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** original commit: {{PgCommitURL|f1b4c77}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235426.GB2842536@tornado.leadboat.com|notified}})<br />
** Fixed by commit c0a8ae7be392aa09dd7e148ff662013e8e148893<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** Fixed by commit 521fd4795e3ec3d0b263b62e5eb58e1557be9c86<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
** Fixed by commit 26ad194cb0a6b955e155d44fb52a74212ce85759<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
** Fixed by commit 3820c63da8d0e59e2bd4476e91968f03be5dd041<br />
<br />
* [http://postgr.es/m/CAMkU=1zrQaPwBN+NcBd3pWCb=vWaiL=mmWfJjDJjh-a7eVr-Og@mail.gmail.com pgbench --progress-timestamp no longer works correctly]<br />
** original commit: {{PgCommitURL|1d63f7d}} (principal author: Tom Lane; owner: Tom Lane {{messageLink|20170411042352.GA2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit feffa0e0795a5a99324890a6dd548ba162ec104c<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235729.GA2842636@tornado.leadboat.com|notified}})<br />
** Fixed by commit 258cef12540fa1cb244881a0f019cefd698c809e<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** original commit: {{PgCommitURL|f35742c}} (principal author: Dilip Kumar; owner: Robert Haas {{messageLink|20170410031734.GB2845039@tornado.leadboat.com|notified}})<br />
** Fixed by commit 4c3b59abf4c476843bca23de7fb66d647627f30e<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
** original commit: {{PgCommitURL|b460f5d}} (principal author: Julien Rouhaud; owner: Robert Haas {{messageLink|20170410031836.GC2845004@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8ff518699f19dd0a5076f5090bac8400b8233f7f<br />
** See also commit 6599c9ac3340b6cd3d86a0a7f866b80a009fecab which attempts to catch other problems of this sort<br />
<br />
* [https://www.postgresql.org/message-id/52d9c443-ec78-5c8a-7a77-0f34aad12b82%40lab.ntt.co.jp RENAME RULE doesn't work with partitioned tables]<br />
** Fixed by commit 02af7857e5694b13c21401d1982ac21d31e27dee<br />
<br />
* [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
** {{messageLink|CA+TgmobTJnasxpRkJxGcHaz85LyqdXBKZRxP6pCCS-UkhcHUBQ@mail.gmail.com|feature request, not bug}}<br />
** implemented in {{PgCommitURL|25542d77dd549940468d1a932809feb9959d717d}}<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** withdrawn<br />
<br />
* [https://www.postgresql.org/message-id/CA%2BTgmobYfFRtcXv1aoXD18%2BRkPU%3Duw39Ajqm1HWyh7V_8QYZ%3DA%40mail.gmail.com pgstathashindex() to handle unused pages in hash index]<br />
** original commit: {{PgCommitURL|e759854}} (principal author: Ashutosh Sharma; owner: Robert Haas {{messageLink|20170412062802.GB2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 9cc27566c1a8d659c15b9eea2413dcc07a7a42c9<br />
<br />
* [https://www.postgresql.org/message-id/30972.1491937807@sss.pgh.pa.us Mishandling of non-parallel-safe initplans/subplans in a parallelized query]<br />
** original commit: {{PgCommitURL|5e6d8d2bb}}<br />
** Fixed by commit 16ebab68862bb5d3595b8c8df083f650d9d7cd20<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** fixed by commits c31671f9b5f6eee9b6726baad2db1795c94839d1, a9254e675bde7dc2d976d207450c559d914c0dd6<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/E1cwSWo-0001hG-Rq@gemulon.postgresql.org Add overview of SCRAM to the FE/BE protocol documentation]. Mention that SASLprep is used on all passwords, UTF-8 or not.<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** fixed by commit 887227a1cc861d87ca0f175cf8bd1447554090eb<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
** fixed by commit 139eb9673cb84c76f493af7e68301ae204199746<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** fixed in pgweb<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** fixed by commit 419a23b478ae760b797188341ddce5b41322684b<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}}<br />
** fixed by commit bf2a691e02d7766f185d9d8e0f092222a5c0a129<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Parallel Query + EXEC_BACKEND + ASLR is broken]<br />
** Problem in 9.6 and later<br />
** Fixed by commits 0ef26bb39 + 32470825d + a74740fbd<br />
<br />
* [https://www.postgresql.org/message-id/CAHE3wgj+2YpFyrg7SAV=-oqTpP2AggT-nRKbR3nkDAt0TA2V6A@mail.gmail.com Different table schema in logical replication crashes]<br />
** fixed by commit e6242c18a5bb08788e6c4cc773952fc8e2a6291a<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** fixed by commit c727f120ff50f624a1ee3abe700d995c18314a0b<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7th<br />
* beta1: wrap May 15th, announce May 18th<br />
<br />
References:<br />
* [https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All original schedule]<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZNLxizOkPy4WKdxwKo40Hz96v5jZ%3D07aLe93JW2dZmRA%40mail.gmail.com feature freeze moved]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29888PostgreSQL 10 Open Items2017-04-14T16:58:53Z<p>Masaofujii: /* Logical Replication */ Add new open item related to logical rep</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
* pg_dump and partitioned tables<br />
** {{messageLink|20170409235057.GA2842536@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
** original commit: {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Stephen Frost, [http://postgr.es/m/20170413150540.GQ9812@tamriel.snowman.net previously Robert Haas])<br />
<br />
=== Logical Replication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|665d1fa}} (principal author: Petr Jelinek; owner: Peter Eisentraut)<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs]<br />
** owner: Andres Freund {{messageLink|20170413045812.GA2917375@tornado.leadboat.com|notified}}<br />
** some issues go back to 9.4; some are new in v10<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** {{messageLink|20170410021658.GB2842636@tornado.leadboat.com|notified}}<br />
** Need to decide how publication membership of tables with inheritance should work.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** {{messageLink|20170410021740.GC2658646@tornado.leadboat.com|notified}}<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
** {{messageLink|20170410022002.GA2845004@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com tablesync patch broke the assumption that logical rep depends on?]<br />
** original commit: {{PgCommitURL|7c4f524}} (principal author: Petr Jelinek; owner: Peter Eisentraut {{messageLink|20170413045605.GD2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEsttg9P9LOOavoc9d6VB1zVmYgfBk=Ljsk-UL9cEf-eA@mail.gmail.com logical replication and PANIC during shutdown checkpoint in publisher]<br />
<br />
* [https://www.postgresql.org/message-id/CAHE3wgj+2YpFyrg7SAV=-oqTpP2AggT-nRKbR3nkDAt0TA2V6A@mail.gmail.com Different table schema in logical replication crashes]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwFDWh_Qr-q_GEMpD+qH=vYPMdVqw=ZOSY3kX_Pna9R9SA@mail.gmail.com some review comments on logical rep code]<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
** {{messageLink|20170410035323.GA2846583@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqSbsCBCxy8-DtwzRxYgTnbGUtY4uFEkLQhG%3DR%3Duo%3Dg8Fw%40mail.gmail.com patch exists]<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** {{messageLink|20170412063327.GA2894486@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqTo6_mk-qNfNMvr96pLi13PrxyR-UJXVP3xxdSkynjVnA%40mail.gmail.com proposal of patch exists]<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
<br />
* [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** owner [https://www.postgresql.org/message-id/20170412225855.oklyfkbwj2dmbrpu@alap3.anarazel.de proposes] classifying this as a non-bug<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170405065518.GC2702846@tornado.leadboat.com|notified}})<br />
** Patch to fix is included.<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** original commit: {{PgCommitURL|e36ddab}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170405065656.GD2702846@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/7064.1492022469@sss.pgh.pa.us Inadequate parallel-safety check for SubPlans]<br />
** original commit: {{PgCommitURL|5e6d8d2bb}}<br />
<br />
* [http://postgr.es/m/CAKJS1f-BmGo410bh5RSPZUvOO0LhmHL2NYmdrC_Jm8pk_FfyCA@mail.gmail.com Allowing extended stats on foreign and partitioned tables]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170414055310.GE2870454@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/CAKOSWN=hUQWwyCJS8a3gTTUkvMkeg2iwSCCs=df0OYxJ_6H0kA@mail.gmail.com Removing ADD GENERATED for identity columns]<br />
** original commit: {{PgCommitURL|3217327}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170414055644.GF2870454@tornado.leadboat.com|notified}})<br />
** Patch exists.<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Parallel Query + EXEC_BACKEND + ASLR is broken]<br />
** Problem in 9.6 and later<br />
** Attempted to fix this with commit 0ef26bb394abedb2745bd838c26ecb3131682bda, but not actually fixed<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** include partitions in information_schema.tables, pg_tables, and psql's \d listing, etc?<br />
** firm support for status quo, lack of firm support for alternatives<br />
<br />
* [https://www.postgresql.org/message-id/071086d7-6462-f0e7-54ca-b633062e317c%40lab.ntt.co.jp Document that foreign table's partition constraint is not enforced locally]<br />
** Patch exists<br />
** documentation is correct, but this would add emphasis to a point<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/12642.1491513976@sss.pgh.pa.us Partitioning optimization broke ConvertRowtypeExpr]<br />
** Fixed by commit 3f902354b08ac788600f0ae54fcbfc1d4e3ea765.<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** Fixed by commit 6f1b9aaae35bfabe2654a8e44ce226c91e7d8bd9<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
** Fixed by commit b2ff37d43cc81348fd8e9d9c5fcc9dfadf790763<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
** Fixed by commit 5a5931533edd2b70bde1f069609f58998dd26fef<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
** Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
** Fixed by commit 5c4488478b182983f290a61fc8cf2ec83548622b<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Fixed by commit 0ef26bb394abedb2745bd838c26ecb3131682bda<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** original commit: {{PgCommitURL|f1b4c77}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235426.GB2842536@tornado.leadboat.com|notified}})<br />
** Fixed by commit c0a8ae7be392aa09dd7e148ff662013e8e148893<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** Fixed by commit 521fd4795e3ec3d0b263b62e5eb58e1557be9c86<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
** Fixed by commit 26ad194cb0a6b955e155d44fb52a74212ce85759<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
** Fixed by commit 3820c63da8d0e59e2bd4476e91968f03be5dd041<br />
<br />
* [http://postgr.es/m/CAMkU=1zrQaPwBN+NcBd3pWCb=vWaiL=mmWfJjDJjh-a7eVr-Og@mail.gmail.com pgbench --progress-timestamp no longer works correctly]<br />
** original commit: {{PgCommitURL|1d63f7d}} (principal author: Tom Lane; owner: Tom Lane {{messageLink|20170411042352.GA2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit feffa0e0795a5a99324890a6dd548ba162ec104c<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235729.GA2842636@tornado.leadboat.com|notified}})<br />
** Fixed by commit 258cef12540fa1cb244881a0f019cefd698c809e<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** original commit: {{PgCommitURL|f35742c}} (principal author: Dilip Kumar; owner: Robert Haas {{messageLink|20170410031734.GB2845039@tornado.leadboat.com|notified}})<br />
** Fixed by commit 4c3b59abf4c476843bca23de7fb66d647627f30e<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
** original commit: {{PgCommitURL|b460f5d}} (principal author: Julien Rouhaud; owner: Robert Haas {{messageLink|20170410031836.GC2845004@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8ff518699f19dd0a5076f5090bac8400b8233f7f<br />
** See also commit 6599c9ac3340b6cd3d86a0a7f866b80a009fecab which attempts to catch other problems of this sort<br />
<br />
* [https://www.postgresql.org/message-id/52d9c443-ec78-5c8a-7a77-0f34aad12b82%40lab.ntt.co.jp RENAME RULE doesn't work with partitioned tables]<br />
** Fixed by commit 02af7857e5694b13c21401d1982ac21d31e27dee<br />
<br />
* [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
** {{messageLink|CA+TgmobTJnasxpRkJxGcHaz85LyqdXBKZRxP6pCCS-UkhcHUBQ@mail.gmail.com|feature request, not bug}}<br />
** implemented in {{PgCommitURL|25542d77dd549940468d1a932809feb9959d717d}}<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** withdrawn<br />
<br />
* [https://www.postgresql.org/message-id/CA%2BTgmobYfFRtcXv1aoXD18%2BRkPU%3Duw39Ajqm1HWyh7V_8QYZ%3DA%40mail.gmail.com pgstathashindex() to handle unused pages in hash index]<br />
** original commit: {{PgCommitURL|e759854}} (principal author: Ashutosh Sharma; owner: Robert Haas {{messageLink|20170412062802.GB2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit 9cc27566c1a8d659c15b9eea2413dcc07a7a42c9<br />
<br />
* [https://www.postgresql.org/message-id/30972.1491937807@sss.pgh.pa.us Mishandling of non-parallel-safe initplans/subplans in a parallelized query]<br />
** original commit: {{PgCommitURL|5e6d8d2bb}}<br />
** Fixed by commit 16ebab68862bb5d3595b8c8df083f650d9d7cd20<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** fixed by commits c31671f9b5f6eee9b6726baad2db1795c94839d1, a9254e675bde7dc2d976d207450c559d914c0dd6<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
* [https://www.postgresql.org/message-id/E1cwSWo-0001hG-Rq@gemulon.postgresql.org Add overview of SCRAM to the FE/BE protocol documentation]. Mention that SASLprep is used on all passwords, UTF-8 or not.<br />
** fixed by commit 4f3b87ab780b95c2cc8a591259baefaff4852037<br />
<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7th<br />
* beta1: wrap May 15th, announce May 18th<br />
<br />
References:<br />
* [https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All original schedule]<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZNLxizOkPy4WKdxwKo40Hz96v5jZ%3D07aLe93JW2dZmRA%40mail.gmail.com feature freeze moved]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29860PostgreSQL 10 Open Items2017-04-12T15:01:10Z<p>Masaofujii: /* Logical Replication */ add new open item regarding logical rep</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas)<br />
<br />
* pg_dump and partitioned tables<br />
** {{messageLink|20170409235057.GA2842536@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
<br />
=== Hash Index ===<br />
<br />
* [https://www.postgresql.org/message-id/CA%2BTgmobYfFRtcXv1aoXD18%2BRkPU%3Duw39Ajqm1HWyh7V_8QYZ%3DA%40mail.gmail.com pgstathashindex() to handle unused pages in hash index]<br />
** original commit: {{PgCommitURL|e759854}} (principal author: Ashutosh Sharma; owner: Robert Haas {{messageLink|20170412062802.GB2870454@tornado.leadboat.com|notified}})<br />
<br />
=== Logical Replication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|665d1fa}} (principal author: Petr Jelinek; owner: Peter Eisentraut)<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** {{messageLink|20170410021615.GA2844913@tornado.leadboat.com|notified}}<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs]<br />
** {{messageLink|20170412063142.GC2870454@tornado.leadboat.com|notified}}<br />
** some issues go back to 9.4; some are new in v10<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** {{messageLink|20170410021658.GB2842636@tornado.leadboat.com|notified}}<br />
** Need to decide how publication membership of tables with inheritance should work.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** {{messageLink|20170410021740.GC2658646@tornado.leadboat.com|notified}}<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
** {{messageLink|20170410022002.GA2845004@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com tablesync patch broke the assumption that logical rep depends on?]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEsttg9P9LOOavoc9d6VB1zVmYgfBk=Ljsk-UL9cEf-eA@mail.gmail.com logical replication and PANIC during shutdown checkpoint in publisher]<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
** {{messageLink|20170410035323.GA2846583@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqSbsCBCxy8-DtwzRxYgTnbGUtY4uFEkLQhG%3DR%3Duo%3Dg8Fw%40mail.gmail.com patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** {{messageLink|20170406051301.GA2658646@tornado.leadboat.com|notified}}<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** {{messageLink|20170412063327.GA2894486@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/CAB7nPqTo6_mk-qNfNMvr96pLi13PrxyR-UJXVP3xxdSkynjVnA%40mail.gmail.com proposal of patch exists]<br />
<br />
* [https://www.postgresql.org/message-id/E1cwSWo-0001hG-Rq@gemulon.postgresql.org Add overview of SCRAM to the FE/BE protocol documentation]. Mention that SASLprep is used on all passwords, UTF-8 or not.<br />
** {{messageLink|20170411042218.GA2870410@tornado.leadboat.com|notified}}<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
<br />
* Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f)<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170405065518.GC2702846@tornado.leadboat.com|notified}})<br />
** Patch to fix is included.<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** original commit: {{PgCommitURL|e36ddab}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170405065656.GD2702846@tornado.leadboat.com|notified}})<br />
<br />
* [https://www.postgresql.org/message-id/30972.1491937807@sss.pgh.pa.us Mishandling of non-parallel-safe initplans/subplans in a parallelized query]<br />
** original commit: {{PgCommitURL|5e6d8d2bb}}<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Parallel Query + EXEC_BACKEND + ASLR is broken]<br />
** Problem in 9.6 and later<br />
** Attempted to fix this with commit 0ef26bb394abedb2745bd838c26ecb3131682bda, but not actually fixed<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** include partitions in information_schema.tables, pg_tables, and psql's \d listing, etc?<br />
** firm support for status quo, lack of firm support for alternatives<br />
<br />
* [https://www.postgresql.org/message-id/071086d7-6462-f0e7-54ca-b633062e317c%40lab.ntt.co.jp Document that foreign table's partition constraint is not enforced locally]<br />
** Patch exists<br />
** documentation is correct, but this would add emphasis to a point<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/12642.1491513976@sss.pgh.pa.us Partitioning optimization broke ConvertRowtypeExpr]<br />
** Fixed by commit 3f902354b08ac788600f0ae54fcbfc1d4e3ea765.<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** Fixed by commit 6f1b9aaae35bfabe2654a8e44ce226c91e7d8bd9<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
** Fixed by commit b2ff37d43cc81348fd8e9d9c5fcc9dfadf790763<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
** Fixed by commit 5a5931533edd2b70bde1f069609f58998dd26fef<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
** Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
** Fixed by commit 5c4488478b182983f290a61fc8cf2ec83548622b<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Fixed by commit 0ef26bb394abedb2745bd838c26ecb3131682bda<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** original commit: {{PgCommitURL|f1b4c77}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235426.GB2842536@tornado.leadboat.com|notified}})<br />
** Fixed by commit c0a8ae7be392aa09dd7e148ff662013e8e148893<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** Fixed by commit 521fd4795e3ec3d0b263b62e5eb58e1557be9c86<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
** Fixed by commit 26ad194cb0a6b955e155d44fb52a74212ce85759<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
** Fixed by commit 3820c63da8d0e59e2bd4476e91968f03be5dd041<br />
<br />
* [http://postgr.es/m/CAMkU=1zrQaPwBN+NcBd3pWCb=vWaiL=mmWfJjDJjh-a7eVr-Og@mail.gmail.com pgbench --progress-timestamp no longer works correctly]<br />
** original commit: {{PgCommitURL|1d63f7d}} (principal author: Tom Lane; owner: Tom Lane {{messageLink|20170411042352.GA2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit feffa0e0795a5a99324890a6dd548ba162ec104c<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235729.GA2842636@tornado.leadboat.com|notified}})<br />
** Fixed by commit 258cef12540fa1cb244881a0f019cefd698c809e<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** original commit: {{PgCommitURL|f35742c}} (principal author: Dilip Kumar; owner: Robert Haas {{messageLink|20170410031734.GB2845039@tornado.leadboat.com|notified}})<br />
** Fixed by commit 4c3b59abf4c476843bca23de7fb66d647627f30e<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
** original commit: {{PgCommitURL|b460f5d}} (principal author: Julien Rouhaud; owner: Robert Haas {{messageLink|20170410031836.GC2845004@tornado.leadboat.com|notified}})<br />
** Fixed by commit 8ff518699f19dd0a5076f5090bac8400b8233f7f<br />
** See also commit 6599c9ac3340b6cd3d86a0a7f866b80a009fecab which attempts to catch other problems of this sort<br />
<br />
* [https://www.postgresql.org/message-id/52d9c443-ec78-5c8a-7a77-0f34aad12b82%40lab.ntt.co.jp RENAME RULE doesn't work with partitioned tables]<br />
** Fixed by commit 02af7857e5694b13c21401d1982ac21d31e27dee<br />
<br />
* [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
** {{messageLink|CA+TgmobTJnasxpRkJxGcHaz85LyqdXBKZRxP6pCCS-UkhcHUBQ@mail.gmail.com|feature request, not bug}}<br />
** implemented in {{PgCommitURL|25542d77dd549940468d1a932809feb9959d717d}}<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** withdrawn<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7th<br />
* beta1: wrap May 15th, announce May 18th<br />
<br />
References:<br />
* [https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All original schedule]<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZNLxizOkPy4WKdxwKo40Hz96v5jZ%3D07aLe93JW2dZmRA%40mail.gmail.com feature freeze moved]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29843PostgreSQL 10 Open Items2017-04-11T15:24:42Z<p>Masaofujii: /* Logical Replication */ Added new open item for logical replication</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|f0e4475}} (principal author: Amit Langote; owner: Robert Haas)<br />
<br />
* pg_dump and partitioned tables<br />
** {{messageLink|20170409235057.GA2842536@tornado.leadboat.com|notified}}<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** {{messageLink|20170409235729.GA2842636@tornado.leadboat.com|notified}}<br />
** Patch exists<br />
<br />
* [https://www.postgresql.org/message-id/52d9c443-ec78-5c8a-7a77-0f34aad12b82%40lab.ntt.co.jp RENAME RULE doesn't work with partitioned tables]<br />
** Patch exists<br />
<br />
<br />
=== Logical Replication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|665d1fa}} (principal author: Petr Jelinek; owner: Peter Eisentraut)<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** {{messageLink|20170410021615.GA2844913@tornado.leadboat.com|notified}}<br />
** Need to figure out the best way to make sure subscriptions are included in backups by default and pg_upgrade works with them<br />
** This should probably wait until we see what's going to happen with initial data copy patch as it modifies the behaviour<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs]<br />
** some issues go back to 9.4; some are new in v10<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** {{messageLink|20170410021658.GB2842636@tornado.leadboat.com|notified}}<br />
** Need to decide how publication membership of tables with inheritance should work.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** {{messageLink|20170410021740.GC2658646@tornado.leadboat.com|notified}}<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
** {{messageLink|20170410022002.GA2845004@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** {{messageLink|20170410024041.GA2845039@tornado.leadboat.com|notified}}<br />
** existing issue, but more relevant now<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com tablesync patch broke the assumption that logical rep depends on?]<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
** {{messageLink|20170410035323.GA2846583@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** {{messageLink|20170406051301.GA2658646@tornado.leadboat.com|notified}}<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** {{messageLink|20170406053605.GC2739265@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/E1cwSWo-0001hG-Rq@gemulon.postgresql.org Add overview of SCRAM to the FE/BE protocol documentation]. Mention that SASLprep is used on all passwords, UTF-8 or not.<br />
** {{messageLink|20170411042218.GA2870410@tornado.leadboat.com|notified}}<br />
<br />
=== Parallel Query ===<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** original commit: {{PgCommitURL|f35742c}} (principal author: Dilip Kumar; owner: Robert Haas {{messageLink|20170410031734.GB2845039@tornado.leadboat.com|notified}})<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
** original commit: {{PgCommitURL|b460f5d}} (principal author: Julien Rouhaud; owner: Robert Haas {{messageLink|20170410031836.GC2845004@tornado.leadboat.com|notified}})<br />
** patch exists<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
<br />
* Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f)<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170405065518.GC2702846@tornado.leadboat.com|notified}})<br />
** Patch to fix is included.<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** original commit: {{PgCommitURL|e36ddab}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170405065656.GD2702846@tornado.leadboat.com|notified}})<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Parallel Query + EXEC_BACKEND + ASLR is broken]<br />
** Problem in 9.6 and later<br />
** Attempted to fix this with commit 0ef26bb394abedb2745bd838c26ecb3131682bda, but not actually fixed<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
* [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
** {{messageLink|CA+TgmobTJnasxpRkJxGcHaz85LyqdXBKZRxP6pCCS-UkhcHUBQ@mail.gmail.com|feature request, not bug}}<br />
** implemented in {{PgCommitURL|25542d77dd549940468d1a932809feb9959d717d}}<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** include partitions in information_schema.tables, pg_tables, and psql's \d listing, etc?<br />
** firm support for status quo, lack of firm support for alternatives<br />
<br />
* [https://www.postgresql.org/message-id/071086d7-6462-f0e7-54ca-b633062e317c%40lab.ntt.co.jp Document that foreign table's partition constraint is not enforced locally]<br />
** Patch exists<br />
** documentation is correct, but this would add emphasis to a point<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/12642.1491513976@sss.pgh.pa.us Partitioning optimization broke ConvertRowtypeExpr]<br />
** Fixed by commit 3f902354b08ac788600f0ae54fcbfc1d4e3ea765.<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** Fixed by commit 6f1b9aaae35bfabe2654a8e44ce226c91e7d8bd9<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
** Fixed by commit b2ff37d43cc81348fd8e9d9c5fcc9dfadf790763<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
** Fixed by commit 5a5931533edd2b70bde1f069609f58998dd26fef<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
** Fixed by commit 60f11b87a2349985230c08616fa8a34ffde934c8<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
** Fixed by commit 5c4488478b182983f290a61fc8cf2ec83548622b<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Fixed by commit 0ef26bb394abedb2745bd838c26ecb3131682bda<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** original commit: {{PgCommitURL|f1b4c77}} (principal author: Amit Langote; owner: Robert Haas {{messageLink|20170409235426.GB2842536@tornado.leadboat.com|notified}})<br />
** Fixed by commit c0a8ae7be392aa09dd7e148ff662013e8e148893<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** Fixed by commit 521fd4795e3ec3d0b263b62e5eb58e1557be9c86<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
** Fixed by commit 26ad194cb0a6b955e155d44fb52a74212ce85759<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
** Fixed by commit 3820c63da8d0e59e2bd4476e91968f03be5dd041<br />
<br />
* [http://postgr.es/m/CAMkU=1zrQaPwBN+NcBd3pWCb=vWaiL=mmWfJjDJjh-a7eVr-Og@mail.gmail.com pgbench --progress-timestamp no longer works correctly]<br />
** original commit: {{PgCommitURL|1d63f7d}} (principal author: Tom Lane; owner: Tom Lane {{messageLink|20170411042352.GA2870454@tornado.leadboat.com|notified}})<br />
** Fixed by commit feffa0e0795a5a99324890a6dd548ba162ec104c<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7th<br />
* beta1: wrap May 15th, announce May 18th<br />
<br />
References:<br />
* [https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All original schedule]<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZNLxizOkPy4WKdxwKo40Hz96v5jZ%3D07aLe93JW2dZmRA%40mail.gmail.com feature freeze moved]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29783PostgreSQL 10 Open Items2017-04-06T15:23:32Z<p>Masaofujii: /* Logical Replication */ Add open item for logical replication</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
* pg_dump and partitioned tables<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
<br />
* sepgsql and partitioned tables<br />
** [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
<br />
* [https://www.postgresql.org/message-id/b3a17254-6849-e542-2353-bde4e880b6a4%40lab.ntt.co.jp Reconsider the error detail shown when ExecConstraints() fails after tuple-routing]<br />
** Patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYrA8SK=KjkVbvKt8hG3Cqsjr-Hnmwa3WXqbziRuwKBLg@mail.gmail.com Declarative partitioning vs. information_schema, etc.]<br />
** One preference seems to be to not include partitions in information_schema.tables, pg_tables, and psql's \d listing,<br />
<br />
* [https://www.postgresql.org/message-id/29588799-a8ce-b0a2-3dae-f39ff6d35922%40lab.ntt.co.jp Dropping a partition may cause deadlock]<br />
** Patch exists<br />
<br />
=== Logical Replication ===<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** Need to figure out the best way to make sure subscriptions are included in backups by default and pg_upgrade works with them<br />
** This should probably wait until we see what's going to happen with initial data copy patch as it modifies the behaviour<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs (all the way back to 9.4)]<br />
** patches for individual issues exist<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** Need to decide how publication membership of tables with inheritance should work.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** causes deadlock against VACUUM FULL, and probably a lot of other cases<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** This issue is halfway fixed and additional patch exists.<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Also an issue for parallelism (in 9.6 already)<br />
** Attempted to fix this with commit 0ef26bb394abedb2745bd838c26ecb3131682bda, but not actually fixed<br />
<br />
* [https://www.postgresql.org/message-id/b7578aaf-726e-61a1-0011-943e92ad08ee@2ndquadrant.com error handling in RegisterBackgroundWorker]<br />
** existing issue, but more relevant now<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoDCnyRJDUY%3DESVVe68AukvOP2dFomTeBFpAd1TiFbjsGg%40mail.gmail.com Interval for launching the table sync worker]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwHEs8jT_6DjYHYmsD2v-rOudstiBB_mtmZbR9Z2QfhCwQ@mail.gmail.com Both launcher and worker don't handle SIGHUP signal and cannot reload the configuration]<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
unless otherwise marked, original commit: {{PgCommitURL|818fd4a}} (principal author: Michael Paquier; owner: Heikki Linnakangas)<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
** {{messageLink|20170406053605.GC2739265@tornado.leadboat.com|notified}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com Letting the client choose the protocol to use during a SASL exchange]<br />
** {{messageLink|20170406051301.GA2658646@tornado.leadboat.com|notified}}<br />
<br />
=== Parallel Query ===<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
<br />
* [https://www.postgresql.org/message-id/20170331185540.zmsue4ndvqtnayqw@alap3.anarazel.de improve test coverage of parallel explain analyze]<br />
<br />
* [https://www.postgresql.org/message-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de improve test coverage of parallel bitmap scan]<br />
<br />
* [https://www.postgresql.org/message-id/flat/24a143e0-c9bb-8f4f-1472-9d6faae4c92e%402ndquadrant.com#24a143e0-c9bb-8f4f-1472-9d6faae4c92e@2ndquadrant.com strange parallel query behavior after OOM crashes]<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com synchronous_standby_names shows unused priority values]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao {{messageLink|20170405064544.GA2702716@tornado.leadboat.com|notified}})<br />
** The priority value is assigned to each standby listed in s_s_names even in quorum commit though those priority values are not used at all. Users can see those priority values in pg_stat_replication. Isn't this confusing? If yes, it might be better to always assign 1 as the priority, for example.<br />
<br />
* Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f)<br />
** original commit: {{PgCommitURL|69f4b9c}} (principal author: Tom Lane; owner: Andres Freund {{messageLink|20170405064755.GA2702846@tornado.leadboat.com|notified}})<br />
** [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** original commit: {{PgCommitURL|96a7128}} (principal author: Michael Paquier; owner: Andrew Dunstan {{messageLink|20170405064941.GB2702846@tornado.leadboat.com|notified}})<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
<br />
* [https://www.postgresql.org/message-id/CAKJS1f9Kk0NF6Fg7TA%3DJUXsjpS9kX6NVu27pb5QDCpOYAvb-Og%40mail.gmail.com extended stats not friendly towards ANALYZE with subset of columns]<br />
** original commit: {{PgCommitURL|7b504eb}} (principal author: Tomas Vondra; owner: Alvaro Herrera {{messageLink|20170405065518.GC2702846@tornado.leadboat.com|notified}})<br />
** Patch to fix is included.<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
** original commit: {{PgCommitURL|e36ddab}} (principal author: Peter Eisentraut; owner: Peter Eisentraut {{messageLink|20170405065656.GD2702846@tornado.leadboat.com|notified}})<br />
<br />
== Design Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** original commit: {{PgCommitURL|3901fd7}} (principal author: Masahiko Sawada; owner: Fujii Masao)<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
== Older Bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
** regression in v9.6, nothing changed from v9.6 beta to v10 beta<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
** present in 9.4 and later<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
** regression in v9.6, nothing new in v10<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
** Not Open-Item worthy, let's do this in v11 if it still feels worthwhile then.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 10beta1 ===<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
*** Reverted by commit f05230752d53c4aa74cffa9b699983bbb6bcb118<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
** Fixed by commit f49bcd4ef3e9a75de210357a4d9bbe3e004db956<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
** Fixed by commit c94e6942cefe7d20c5feed856e27f672734b1e2b<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements for partitioning]<br />
** Fixed by commit 8f18a880a5f138d4da94173d15514142331f8de6<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
** Fixed by commit 25dc142a49c60c3107480c487cd8444dc83f9bdf<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** Fixed by commit 93cd7684ee2bba227fa371daa81b88f25456dcb2<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** Fixed by commit 75a1cbdc3cfca1e815da6dfa5d7e96d82a6b0725<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** Fixed by commit 633e15ea0f1bf2e1d70441fe9da8781befebd6e9</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=29690PostgreSQL 10 Open Items2017-03-30T16:52:25Z<p>Masaofujii: /* Logical Replication */ added the oversight in logical replication</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Partitioning ===<br />
<br />
* [https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e@lab.ntt.co.jp Partitioning tables create a file on-disk, which remains empty and has no purpose. Those relations don't need any storage]<br />
<br />
* pg_dump and partitioned tables<br />
** [https://www.postgresql.org/message-id/7682253a-6f79-6a92-00aa-267c4c412870%40lab.ntt.co.jp pg_dump should not emit ALTER TABLE ONLY for a partitioned table in case of attribute changes and inheritable constraints]<br />
*** patch exists<br />
** [https://www.postgresql.org/message-id/20170217133251.GK9812%40tamriel.snowman.net pg_dump TAP tests around partitioning]<br />
<br />
* sepgsql and partitioned tables<br />
** [https://postgr.es/m/20170309144718.GE9812@tamriel.snowman.net sepgsql and partitioned tables]<br />
<br />
* postgres_fdw, partitioned tables and IMPORT SCHEMA<br />
** [https://postgr.es/m/20170309141531.GD9812@tamriel.snowman.net postgres_fdw IMPORT SCHEMA and partitioned tables]<br />
<br />
* [https://www.postgresql.org/message-id/a6f99cdb-21e7-1d65-1381-91f2cfa156e2%40lab.ntt.co.jp Documentation improvements]<br />
** Patch exists<br />
<br />
* Reconsider ON CONFLICT on partitioned tables<br />
** [https://www.postgresql.org/message-id/ff3dc21d-7204-c09c-50ac-cf11a8c45c81%40lab.ntt.co.jp Crash when leaf partition has an index]<br />
<br />
=== Logical Replication ===<br />
<br />
* [https://www.postgresql.org/message-id/20170217020415.GI9812@tamriel.snowman.net pg_dump and SUBSCRIPTIONS]<br />
** Need to figure out the best way to make sure subscriptions are included in backups by default and pg_upgrade works with them<br />
** This should probably wait until we see what's going to happen with initial data copy patch as it modifies the behaviour<br />
<br />
* [https://www.postgresql.org/message-id/51f65289-54f8-2256-d107-937d662d69f1%402ndquadrant.com snapshot builder has bugs (all the way back to 9.4)]<br />
<br />
* [https://www.postgresql.org/message-id/flat/92ea7dd8-70b9-16c6-9327-e67e56209f33%40lab.ntt.co.jp publications vs inheritance]<br />
** Need to decide how publication membership of tables with inheritance should work.<br />
<br />
* [https://www.postgresql.org/message-id/flat/CA%2BTgmoarXTa3F5ybQ98DtUDKVMUpg5JoDykPXUaEr9z_8OyYWQ%40mail.gmail.com add synchronous_commit control for logical apply]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/flat/b235fa69-147a-5e09-f8f3-3f780a1abb2e@2ndquadrant.com origin tracking is slightly off in logical apply]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB2ZbCCqOx%3DbgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA%40mail.gmail.com Replication status in logical replication]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/a2355846-e5b1-184c-71a4-882f514b5948%402ndquadrant.com ALTER SUBSCRIPTION ... WITH (SLOT NAME = ...) crashes apply worker]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/20170316085322.crffknkgee5s6air@alap3.anarazel.de Logical replication + EXEC_BACKEND + ASLR is broken]<br />
** Also an issue for parallelism (in 9.6 already)<br />
<br />
* [https://www.postgresql.org/message-id/13592.1490851519@sss.pgh.pa.us Broken locking design for accesses to pg_subscription_rel]<br />
** causes deadlock against VACUUM FULL, and probably a lot of other cases<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwGA2tz-iQ90ofgX0Q1TuZLyr+GCX+T1=PE+ogUKVSRpZA@mail.gmail.com logical replication worker and statistics]<br />
<br />
=== SCRAM-SHA-256 Authentication ===<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSP+MHqg=dKoNOZu75j2mGAEW622GYz45Mv2V_XOao-9g@mail.gmail.com CREATE/ALTER ROLE PASSWORD ('value' USING 'method')], extension of this DDL to enforce type of password without changing password_encryption.<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqSByyEmAVLtEf1KxTRh=PWNKiWKEKQR=e1yGehz=wbymQ@mail.gmail.com SASLprep]<br />
<br />
* [https://www.postgresql.org/message-id/CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com Switch use of "encrypted" to "hash" for passwords in documentation]<br />
<br />
* {{messageLink|b081887e-1712-3aa4-7dbe-e012333d50e4@iki.fi|pg_hba.conf syntax}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wfBgFPbfAMYZQE78p=VhZX7nN86aWkp0QcCp=+KxZ=bg@mail.gmail.com \password and PQencryptPassword]<br />
<br />
* [https://www.postgresql.org/message-id/20170321135742.GB23103@e733.localdomain Errors with valgrind]<br />
<br />
=== Hash Indexes ===<br />
<br />
* [https://www.postgresql.org/message-id/CAA4eK1%2BVE_TDRLWpyeOf%2B7%2B6if68kgPNwO4guKo060rm_t3O5w%40mail.gmail.com page inspect to show appropriate type of page]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0P%3DV2LhtyeMXd295fhisp%3DNWUhRVJ9EZQCDowWiY9rSohQ%40mail.gmail.com Failed assertion in _hash_kill_items/MarkBufferDirtyHint]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAE9k0PnmPDXfvf8HDObme7q_Ewc4E26ukHXUBPySoOs0ObqqaQ%40mail.gmail.com inconsistent page found on STANDBY server]<br />
** patch exists<br />
<br />
=== Parallel Query ===<br />
<br />
* [https://www.postgresql.org/message-id/6ecd6f17-0dcf-1de7-ded8-0de7db1ddc88%402ndquadrant.com crashes due to setting max_parallel_workers=0]<br />
<br />
* [https://www.postgresql.org/message-id/CAFiTN-suK%2BMod_noGy8LpmkSzgvzwhGfNZ0K6vf_gX6rkw2jxA%40mail.gmail.com Problem in Parallel Bitmap Heap Scan]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoZfPOu62bR71bahf90ivOUxXpYOh0RqDiue0+dVVPNrWg@mail.gmail.com dsa.c needs a visit from the message style police]<br />
<br />
=== Documentation tool chain ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/alpine.DEB.2.20.1702161846410.29507@lancre/ web site CSS issues]<br />
<br />
=== Other ===<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** There will be still many source comments and documentations that we7c030783a5bd07cadffc2a1018bc33119a4c7505 need to update, for example, in high-availability.sgml. We need to check and update them throughly.<br />
<br />
* Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f)<br />
** [https://postgr.es/m/CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com Query fails when SRFs are part of FROM clause]<br />
<br />
* pg_dump and data durability, with addition of --no-sync option<br />
** [https://www.postgresql.org/message-id/CAB7nPqTUOpF792rDOnBkswZ%3DZgHwxdB01OQU2tAF1KU4iUuLrw%40mail.gmail.com Regression tests should use --no-sync as much as possible]<br />
<br />
* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp standby can fail to reconnect even with replication slots]<br />
** patch exists<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1wXkKUKBHWBYzET3D9OViyDg8DcVL-wKEqk2uyoMrzr_A@mail.gmail.com Crash recovery can leave everlasting empty pages]<br />
** The pages are actually empty but FSM says that they have no room for new data and ALL_FROZEN. ALL_FROZEN prevents autovacuum from fixing FSM.<br />
<br />
* [https://www.postgresql.org/message-id/20170321.192419.96677899.horiguchi.kyotaro%40lab.ntt.co.jp Logical replication between differrent encodings fails]<br />
** This issue is halfway fixed and additional patch exists.<br />
<br />
== Resolved before beta1 ==<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1yURZZONoeLXhPsp2AkqR5MNAXiCiTVnrt2LGd6qD1b8w@mail.gmail.com pg_upgrade is broken because of renaming of pg_resetxlog to pg_resetwal]<br />
** Fixed by commit b877761.<br />
<br />
* [https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24#1803D792815FC24D871C00D17AE95905AC5FAE@g01jpexmbkw24 PQsendQuery fails when it should not if target_session_attrs is set to read-write]<br />
** Fixed by commit 1de0a4e.<br />
<br />
* [https://www.postgresql.org/message-id/CAM2+6=U72y2_Jni2p+meqTvvk=r_=Wd4orvzz5YL0b3WFx+gcA@mail.gmail.com Substantial bloat in postgres_fdw regression test runtime]<br />
** Fixed by commit aa7f593b1ffa9717bd5570174944c06c482d1c1f.<br />
<br />
* [https://www.postgresql.org/message-id/9f9dc7ae-14f0-4a25-5485-964d9bfc19bd%40lab.ntt.co.jp Error detail shown when partition not found]<br />
** Fixed by commit 5a73e17317e91912b2755f7960d5bf31d374cf31.<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoD%2BVO93zZ4ZQtZQb-jZ_wMko3OgGdx1MXO4T%2B8q_zHDDA%40mail.gmail.com DROP SUBSCRIPTION and ROLLBACK]<br />
** Fixed by commit 272adf4f9cd67df323ae57ff3dee238b649d3b73.<br />
<br />
* [https://www.postgresql.org/message-id/6c420206-45d7-3f56-8325-4bd7b76483ba%40lab.ntt.co.jp Dropping partitioned tables without CASCADE]<br />
** Fixed by commit 8b4d582d279d784616c228be58af1e39aa430402.<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm=15e9L695yVCO-_OkBVbsPupyXqzYWzzDmj-bdJ6o2+Pw@mail.gmail.com pg_recvlogical.c doesn't build with --disable-integer-datetimes]<br />
** Fixed by commit b6aa17e0ae367afdcea07118e016111af4fa6bc3 and c29aff959dc64f7321062e7f33d8c6ec23db53d3<br />
<br />
* [https://www.postgresql.org/message-id/20170207201932.GH9812@tamriel.snowman.net pg_dump and PUBLICATIONS]<br />
** Fixed by commit 05227e0c345247c9e9ff91445850f414e2b0bb70<br />
<br />
* [https://www.postgresql.org/message-id/CA+TgmoYpwN0AkaCqhAEVuxtHqGkz=yJzgQxbvucEQMPE-tLkEA@mail.gmail.com simplehash performance regressions]<br />
** Fixed by commit d4c62a6b623d6eef88218158e9fa3cf974c6c7e5<br />
<br />
* [https://www.postgresql.org/message-id/CAGz5QCLJJ1NhVQjQSreF-UoQyVoN6Krg54gZrr5-Ha5PqP2ksw@mail.gmail.com exposing wait events for non-backends]<br />
** Fixed by commit fc70a4b0df38bda6a13941f1581f25fbb643c7f3<br />
<br />
* [https://www.postgresql.org/message-id/b3d37313-acf0-d8fd-783f-c32f7c0667e6@lab.ntt.co.jp Partitioning vs INSERT ON CONFLICT]<br />
** Fixed by commit 8355a011a0124bdf7ccbada206a967d427039553<br />
<br />
* [https://www.postgresql.org/message-id/c72cbc58-9866-0622-86c1-f01cc4064e73%40lab.ntt.co.jp Bug in list partitioning tuple-routing]<br />
** Fixed by commit 7ecb7143589f38d679bb566311dfa9be1a650fd5<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU%3D1w-9Qe%3DFf1o6bSaXpNO9wqpo7_9GL8_CVhw4BoVVHasqg%40mail.gmail.com segfault in hot_standby for hash indexes]<br />
** Fixed by commit c4c51541e22bf7f2da8ecf6986271687b0d7a90e<br />
<br />
* [https://www.postgresql.org/message-id/CAEepm%3D23%3DvGz%3DCgVurPxBGV6SeOJ7YxSaAJKr_aH%2Bf2cV4zrow%40mail.gmail.com attaching to DSA area that was already destroyed]<br />
** Fixed by commit fddf45b38097d14301d249fbeebca32e40233bd2</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_10_Open_Items&diff=28814PostgreSQL 10 Open Items2016-12-20T14:28:21Z<p>Masaofujii: Add open items for quorum commit feature</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [https://www.postgresql.org/message-id/c2c7191b-5ca0-b37a-9e9d-4df15ffb554b%40lab.ntt.co.jp Oddity in EXPLAIN for foreign/custom join pushdown plans]<br />
** postgres_fdw produces incorrect aliases for joining relations shown in EXPLAIN for some join pushdown queries<br />
** [https://www.postgresql.org/message-id/b4b04e83-5eb4-7dd6-2951-32acadea4e7b@lab.ntt.co.jp low-priority issue; let's leave this for v10]<br />
<br />
* Integer overflow in enlargeStringInfo<br />
** {{messageLink|1706e85e-60d2-494e-8a64-9af1e1b2186e@manitou-mail.org|thinko in overflow logic}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Which synchronous replication method, priority or quorum, should be chosen when neither FIRST nor ANY is specified in synchronous_standby_names?]<br />
** Right now, a priority-based sync replication is chosen for keeping backward compatibility. However some hackers argued to change this decision so that a quorum commit is chosen because they think that most users prefer to a quorum.<br />
<br />
* [https://www.postgresql.org/message-id/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com Improve the docs and comments for quorum-based sync replication]<br />
** There will be still many source comments and documentations that we need to update, for example, in high-availability.sgml. We need to check and update them throughly.</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.6_Open_Items&diff=27252PostgreSQL 9.6 Open Items2016-03-23T04:25:55Z<p>Masaofujii: Added the open item related to visibility map</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/CAB-SwXZh44_2ybvS5Z67p_CDz=XFn4hNAD=CnMEF+QqkXwFrGg@mail.gmail.com commit ac1d794 hurts performance]<br />
<br />
* [https://commitfest.postgresql.org/10/582/ incorrect doc for pgbench log format]. The part about latency limit description in the log format should be backported to 9.5.<br />
<br />
* [http://www.postgresql.org/message-id/CAKcux6=uEP9Op+8N6XHQ8kV4YzUi-E1RBWE8L+3oUeyYAhJ1fw@mail.gmail.com crash/assertion failure in postgres_fdw with three-table joins]<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqSAZ9HnUcMoUa30JO2wJ8MnREm18p2a7McRA-ZrJxj3Vw@mail.gmail.com Recovery test failure for recovery_min_apply_delay]<br />
<br />
* [http://www.postgresql.org/message-id/CAD21AoDpZ6Xjg=gFrGPnSn4oTRRcwK1EBrWCq9OqOHuAcMMC=w@mail.gmail.com Suspicious behaviour on applying XLOG_HEAP2_VISIBLE]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.6beta1 ===<br />
<br />
=== resolved before 9.6beta1 ===<br />
<br />
== Older bugs ==<br />
<br />
== Non-bugs ==<br />
<br />
[[Category:PostgreSQL_9.6]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=26276PostgreSQL 9.5 Open Items2015-11-02T15:54:12Z<p>Masaofujii: /* Other Open Issues */ Add new open item related to track_commit_timestamp</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Due to how locking is done in combination with updates and snapshots and RLS, it's possible, with the right timing and in the absence of any additional independent locking, to lock a row and then to see the updated results of that row where the access to that row has been removed. Discussed by Peter with Heikki and Andres where the agreement was that it was not a serious issue but documentation should be added to explain it.<br />
** Stephen proposed initial wording to take care of this and will provide a docpatch.<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* Documentation tweaks - [http://www.postgresql.org/message-id/CAM3SWZScpWzQ-7EJC77vwqzZ1GO8GNmURQ1QqDQ3wRn7AbW1Cg@mail.gmail.com patch for all issues has been posted]<br />
** [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition] - The consensus is to treat the problem as a limitation and document it.<br />
** Peter suggests that "ON CONSTRAINT constraint_name" ought to be discouraged by INSERT documentation. Early signs are that users do this more than we'd prefer. Naming a constraint does not benefit from the flexibility of inference in handling future edge-cases, that may occur during migrations and so on. Naming a constraint was always considered an escape hatch only (primarily for the benefit of exclusion constraints + DO NOTHING variant, the only place where it's essential).<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
** the crash case requires changes to postgres_fdw that are not and presumably never will be in 9.5, so not clear this is a blocker for 9.5<br />
** it might be sufficient to consider join pushdown as unsupported for now when select-for-update is involved<br />
* [http://www.postgresql.org/message-id/CAB7nPqSyLo4Jzp7-2hJh24YEU99tspkWj7vtj7NYTGcXasw2hg@mail.gmail.com pg_rewind exiting with error code 1 when source and target are on the same timeline]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yyPy5DNmfd-r4meNaJsyuHzkvy1BD-aT=1qR_6_68UZQ@mail.gmail.com psql extended wrapped format] off by one error in line wrapping<br />
* {{messageLink|20151029065903.GC770464@tornado.leadboat.com|Finish multixact truncation rework}} [Noah]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEsKDoYFarJjQ4dvH2ZiDxxK0ZcBP4cV2ahdje5pRW2JA@mail.gmail.com another strange behavior with track_commit_timestamp]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5beta1 ===<br />
* [http://www.postgresql.org/message-id/CAJrrPGf49McMA=jAThY1rSdjKvad3Jj5mVn1_OD9A9M5v2PeSQ@mail.gmail.com Queries including simple UNION ALL against tables which have RLS policies could fail with an ERROR]<br />
* [http://www.postgresql.org/message-id/20151014160818.3034.13514@wrigleys.postgresql.org Crash with recursive call of jsonb_object_agg in plpgsql]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEb3HSEBEu3mWYKjxBySr9zfNd4-AcmpqXJhEoDBk9w1w@mail.gmail.com Strange behavior on track_commit_timestamp]<br />
* [http://git.postgresql.org/pg/commitdiff/21a4e4a4c9fe417e2462b6f90f6b0e49e32ceba6 Oversize item computation needs more testing (c.f. ereport(ERROR) calls in brin_getinsertbuffer)]<br />
* {{messageLink|CAE2gYzyB39Q9up_-TO6FKhH44pcAM1x6n_Cuj15qKoLoFihUVg@mail.gmail.com|Document the `inclusion` framework}}<br />
<br />
=== resolved after 9.5alpha2 ===<br />
<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various issues with EXCLUDED.* targetlist]<br />
* [http://www.postgresql.org/message-id/flat/55C07835.3010409@lab.ntt.co.jp report of issue with dropped columns].<br />
* [http://www.postgresql.org/message-id/CAB7nPqQ3o10SY6NVdU4pjq85GQTN5tbbkq2gnNUh2fBNU3rKyQ@mail.gmail.com pg_receivexlog --if-not-exists plays with pointer dereference], pointed out by Coverity.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [https://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']. (Actually the problem is effective index corruption; see [https://www.postgresql.org/message-id/20150731194524.GB2441@postgresql.org 20150731194524] for details)<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors] - release note patch committed.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c26170668c82eaaf28b6efbf76c5d1c206c27121 Link $(WIN32RES) into single-file modules only when PGFILEDESC is set.]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b8fe12a83622b350dc6849f8bb933bd8a86c1424 Reconcile nodes/*funcs.c]<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/19440.1438917759@sss.pgh.pa.us brin_page_items() is unsafe against cache flushes]<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
** This now appears to have been a [http://www.postgresql.org/message-id/CAN=rtBjFfoNn2vEXSYRu=21GcvmzBxrYygc4pORAuFRPu9ObNA@mail.gmail.com false alarm] caused by local code changes, and perhaps an inconsistent build.<br />
* [http://www.postgresql.org/message-id/CAB7nPqS_kF7vJaQA6qNbcuQnr5B6JBDyxAz5MuXPsB3KtmoBbA@mail.gmail.com commit_ts and its dereferenced pointers]<br />
* [http://www.postgresql.org/message-id/28006.1433903315@sss.pgh.pa.us PL/Python docs still describe pre-9.5 float conversion semantics]<br />
* [http://www.postgresql.org/message-id/CAHGQGwG6YPSvYZHPFxQY+zUe3EN_Xz77FLgTKe5yxXCC44VOTw@mail.gmail.com CancelBackup() and tablespace_map file]<br />
* Remove row_security=force [Noah]<br />
* {{messageLink|20150910192313.GT3685@tamriel.snowman.net|Remove SECURITY_ROW_LEVEL_DISABLED; make ri_triggers.c subject to policies}} [Noah]<br />
* {{messageLink|20150914072916.GC3553126@tornado.leadboat.com|Make BYPASSRLS more like table-owner bypass?}} [Noah]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
** Needs further rebasing following changes to restrictive policies from extensions<br />
** Not a behavioral change, code cleanup, need to determine if it should be done for 9.5 or just in master.<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
* ON CONFLICT ... UPDATE on tables with oids didn't work<br />
* [RLS] Leave one or more policies in the regression database, so that the pg_upgrade test suite exercises pg_dump support<br />
* [http://www.postgresql.org/message-id/CAA-aLv755gg9LwLzvrmRX_xH+4e=BkaA3VLrof8aEMJ9-J5TtA@mail.gmail.com Can't connect with PGSSLMODE=require on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwFuzfO4JscM9LCAmCDCxp_MfLvN4QdB+xWsS-FijbjTYQ@mail.gmail.com track_commit_timestamp tracks COMMIT PREPARED in standby server, but not in master server.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwHereDzzzmfxEBYcVQu3oZv6vZcgu1TPeERWbDc+gQ06g@mail.gmail.com The behavior of the standby when track_commit_timestamp is flipped in the master is weird.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** Questions have been raised about how UPDATE, DELETE, etc, USING clauses are independent of the SELECT USING clause; specifically, if the SELECT USING clause should always be applied first and then the UPDATE and DELETE USING clauses be combined with the SELECT USING clause. The current approach, where they are independent, means that it's possible to set up policies to allow "blind" UPDATEs or DELETEs, where a row could be updated or deleted even though it can't be "seen" through the SELECT USING policy. While the consensus was not overwhelming, the prevailing opinion appears to be that the current approach is very easy to explain, reason about, and flexible even if it does allow such 'blind' changes.<br />
** There was further discussion about modifying UPDATE policies, specifically, to allow the WITH CHECK policy to reference both the 'old' and 'new' versions of the row. That looks like it may be a useful future enhancement but not to be addressed at this time.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Next steps are either additional documentation or review and comment of the existing approach and/or the proposals suggested.<br />
** Additional documentation is being worked on to better explain RETURNING, the blind updates/deletes, etc.<br />
* {{messageLink|55D5473F.2090807@2ndquadrant.com|Hash joins try to allocate too much memory}}<br />
* {{messageLink|CAA-aLv59dToy02HNQd2wvFO8S5ZpLwQwtnsdoCGKehp7tCHrxA@mail.gmail.com|jsonb_set bug when using string value for path to array element}}<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Add DDL-controlled, per-table policy forcing<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
** Decision has been taken to make pg_xlog behave as a repository even if it is detected as a soft link. Switched as such by 0e42397.<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6. Fixed as 426746b.<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched to SUSET.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Older bugs ==<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/20150728085711.GB20627@msg.df7cb.de pg_rewind tests are unstable]<br />
** Patch committed as 582fbff, which should fix the reported symptom.<br />
** {{messageLink|20150903062500.GB2973274@tornado.leadboat.com|pg_ctl timeouts}} remain a potential source of pg_rewind test suite instability, but the pg_ctl suite is also affected, back to 9.4.<br />
<br />
== Non-bugs ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
* Refactoring speculative insertion with unique indexes a little - [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Idea formally proposed, patch posted]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
** this would be good to fix up, but [http://www.postgresql.org/message-id/20151014101436.GL10323@awork2.anarazel.de not a release blocker] and subsequent discussion<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=26057PostgreSQL 9.5 Open Items2015-10-13T16:45:33Z<p>Masaofujii: /* Other Open Issues */ Added new item regarding track_commit_timestamp</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Due to how locking is done in combination with updates and snapshots and RLS, it's possible, with the right timing and in the absence of any additional independent locking, to lock a row and then to see the updated results of that row where the access to that row has been removed. Discussed by Peter with Heikki and Andres where the agreement was that it was not a serious issue but documentation should be added to explain it.<br />
** Stephen proposed initial wording to take care of this and will provide a docpatch.<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* Documentation tweaks - [http://www.postgresql.org/message-id/CAM3SWZScpWzQ-7EJC77vwqzZ1GO8GNmURQ1QqDQ3wRn7AbW1Cg@mail.gmail.com patch for all issues has been posted]<br />
** [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition] - The consensus is to treat the problem as a limitation and document it.<br />
** Peter suggests that "ON CONSTRAINT constraint_name" ought to be discouraged by INSERT documentation. Early signs are that users do this more than we'd prefer. Naming a constraint does not benefit from the flexibility of inference in handling future edge-cases, that may occur during migrations and so on. Naming a constraint was always considered an escape hatch only (primarily for the benefit of exclusion constraints + DO NOTHING variant, the only place where it's essential).<br />
<br />
=== Open BRIN Issues ===<br />
<br />
* Oversize item computation needs more testing (c.f. ereport(ERROR) calls in brin_getinsertbuffer)<br />
* {{messageLink|CAE2gYzyB39Q9up_-TO6FKhH44pcAM1x6n_Cuj15qKoLoFihUVg@mail.gmail.com|Document the `inclusion` framework}}<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
** the crash case requires changes to postgres_fdw that are not and presumably never will be in 9.5, so not clear this is a blocker for 9.5<br />
** it might be sufficient to consider join pushdown as unsupported for now when select-for-update is involved<br />
* [http://www.postgresql.org/message-id/CAHGQGwEb3HSEBEu3mWYKjxBySr9zfNd4-AcmpqXJhEoDBk9w1w@mail.gmail.com Strange behavior on track_commit_timestamp]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5beta1 ===<br />
* [http://www.postgresql.org/message-id/CAJrrPGf49McMA=jAThY1rSdjKvad3Jj5mVn1_OD9A9M5v2PeSQ@mail.gmail.com Queries including simple UNION ALL against tables which have RLS policies could fail with an ERROR]<br />
<br />
=== resolved after 9.5alpha2 ===<br />
<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various issues with EXCLUDED.* targetlist]<br />
* [http://www.postgresql.org/message-id/flat/55C07835.3010409@lab.ntt.co.jp report of issue with dropped columns].<br />
* [http://www.postgresql.org/message-id/CAB7nPqQ3o10SY6NVdU4pjq85GQTN5tbbkq2gnNUh2fBNU3rKyQ@mail.gmail.com pg_receivexlog --if-not-exists plays with pointer dereference], pointed out by Coverity.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [https://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']. (Actually the problem is effective index corruption; see [https://www.postgresql.org/message-id/20150731194524.GB2441@postgresql.org 20150731194524] for details)<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors] - release note patch committed.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c26170668c82eaaf28b6efbf76c5d1c206c27121 Link $(WIN32RES) into single-file modules only when PGFILEDESC is set.]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b8fe12a83622b350dc6849f8bb933bd8a86c1424 Reconcile nodes/*funcs.c]<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/19440.1438917759@sss.pgh.pa.us brin_page_items() is unsafe against cache flushes]<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
** This now appears to have been a [http://www.postgresql.org/message-id/CAN=rtBjFfoNn2vEXSYRu=21GcvmzBxrYygc4pORAuFRPu9ObNA@mail.gmail.com false alarm] caused by local code changes, and perhaps an inconsistent build.<br />
* [http://www.postgresql.org/message-id/CAB7nPqS_kF7vJaQA6qNbcuQnr5B6JBDyxAz5MuXPsB3KtmoBbA@mail.gmail.com commit_ts and its dereferenced pointers]<br />
* [http://www.postgresql.org/message-id/28006.1433903315@sss.pgh.pa.us PL/Python docs still describe pre-9.5 float conversion semantics]<br />
* [http://www.postgresql.org/message-id/CAHGQGwG6YPSvYZHPFxQY+zUe3EN_Xz77FLgTKe5yxXCC44VOTw@mail.gmail.com CancelBackup() and tablespace_map file]<br />
* Remove row_security=force [Noah]<br />
* {{messageLink|20150910192313.GT3685@tamriel.snowman.net|Remove SECURITY_ROW_LEVEL_DISABLED; make ri_triggers.c subject to policies}} [Noah]<br />
* {{messageLink|20150914072916.GC3553126@tornado.leadboat.com|Make BYPASSRLS more like table-owner bypass?}} [Noah]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
** Needs further rebasing following changes to restrictive policies from extensions<br />
** Not a behavioral change, code cleanup, need to determine if it should be done for 9.5 or just in master.<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
* ON CONFLICT ... UPDATE on tables with oids didn't work<br />
* [RLS] Leave one or more policies in the regression database, so that the pg_upgrade test suite exercises pg_dump support<br />
* [http://www.postgresql.org/message-id/CAA-aLv755gg9LwLzvrmRX_xH+4e=BkaA3VLrof8aEMJ9-J5TtA@mail.gmail.com Can't connect with PGSSLMODE=require on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwFuzfO4JscM9LCAmCDCxp_MfLvN4QdB+xWsS-FijbjTYQ@mail.gmail.com track_commit_timestamp tracks COMMIT PREPARED in standby server, but not in master server.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwHereDzzzmfxEBYcVQu3oZv6vZcgu1TPeERWbDc+gQ06g@mail.gmail.com The behavior of the standby when track_commit_timestamp is flipped in the master is weird.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** Questions have been raised about how UPDATE, DELETE, etc, USING clauses are independent of the SELECT USING clause; specifically, if the SELECT USING clause should always be applied first and then the UPDATE and DELETE USING clauses be combined with the SELECT USING clause. The current approach, where they are independent, means that it's possible to set up policies to allow "blind" UPDATEs or DELETEs, where a row could be updated or deleted even though it can't be "seen" through the SELECT USING policy. While the consensus was not overwhelming, the prevailing opinion appears to be that the current approach is very easy to explain, reason about, and flexible even if it does allow such 'blind' changes.<br />
** There was further discussion about modifying UPDATE policies, specifically, to allow the WITH CHECK policy to reference both the 'old' and 'new' versions of the row. That looks like it may be a useful future enhancement but not to be addressed at this time.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Next steps are either additional documentation or review and comment of the existing approach and/or the proposals suggested.<br />
** Additional documentation is being worked on to better explain RETURNING, the blind updates/deletes, etc.<br />
* {{messageLink|55D5473F.2090807@2ndquadrant.com|Hash joins try to allocate too much memory}}<br />
* {{messageLink|CAA-aLv59dToy02HNQd2wvFO8S5ZpLwQwtnsdoCGKehp7tCHrxA@mail.gmail.com|jsonb_set bug when using string value for path to array element}}<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Add DDL-controlled, per-table policy forcing<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
** Decision has been taken to make pg_xlog behave as a repository even if it is detected as a soft link. Switched as such by 0e42397.<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6. Fixed as 426746b.<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched to SUSET.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Older bugs ==<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/20150728085711.GB20627@msg.df7cb.de pg_rewind tests are unstable]<br />
** Patch committed as 582fbff, which should fix the reported symptom.<br />
** {{messageLink|20150903062500.GB2973274@tornado.leadboat.com|pg_ctl timeouts}} remain a potential source of pg_rewind test suite instability, but the pg_ctl suite is also affected, back to 9.4.<br />
<br />
== Non-bugs ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25832PostgreSQL 9.5 Open Items2015-09-15T14:26:35Z<p>Masaofujii: Fixed the confusing log messages related to tablespace_map file</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** Questions have been raised about how UPDATE, DELETE, etc, USING clauses are independent of the SELECT USING clause; specifically, if the SELECT USING clause should always be applied first and then the UPDATE and DELETE USING clauses be combined with the SELECT USING clause. The current approach, where they are independent, means that it's possible to set up policies to allow "blind" UPDATEs or DELETEs, where a row could be updated or deleted even though it can't be "seen" through the SELECT USING policy. While the consensus was not overwhelming, the prevailing opinion appears to be that the current approach is very easy to explain, reason about, and flexible even if it does allow such 'blind' changes.<br />
** There was further discussion about modifying UPDATE policies, specifically, to allow the WITH CHECK policy to reference both the 'old' and 'new' versions of the row. That looks like it may be a useful future enhancement but not to be addressed at this time.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Next steps are either additional documentation or review and comment of the existing approach and/or the proposals suggested.<br />
** Additional documentation is being worked on to better explain RETURNING, the blind updates/deletes, etc.<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Due to how locking is done in combination with updates and snapshots and RLS, it's possible, with the right timing and in the absence of any additional independent locking, to lock a row and then to see the updated results of that row where the access to that row has been removed. Discussed by Peter with Heikki and Andres where the agreement was that it was not a serious issue but documentation should be added to explain it.<br />
** Stephen proposed initial wording to take care of this and will provide a docpatch.<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
** Needs further rebasing following changes to restrictive policies from extensions<br />
** Not a behavioral change, code cleanup, need to determine if it should be done for 9.5 or just in master.<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Only item 5 open- questioned if "row-level-security disabled" security context was necessary<br />
** Patch proposed to address #5 which removes the new security context<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various issues with EXCLUDED.* targetlist]<br />
** "excluded.* wholerow var" bug still must be addressed, plus [http://www.postgresql.org/message-id/flat/55C07835.3010409@lab.ntt.co.jp report of issue with dropped columns]. Note that there is also a related issue with OID columns (when tables have OIDs). These are now consolidated into one item here because joined-up thinking is required to fix all these superficially different issues at once.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open pg_rewind Issues ===<br />
* [http://www.postgresql.org/message-id/20150728085711.GB20627@msg.df7cb.de pg_rewind tests are unstable]<br />
<br />
=== Open BRIN Issues ===<br />
<br />
* Oversize item computation needs more testing (c.f. ereport(ERROR) calls in brin_getinsertbuffer)<br />
* {{messageLink|CAE2gYzyB39Q9up_-TO6FKhH44pcAM1x6n_Cuj15qKoLoFihUVg@mail.gmail.com|Document the `inclusion` framework}}<br />
<br />
=== Open track_commit_timestamp Issues ===<br />
* [http://www.postgresql.org/message-id/CAHGQGwFuzfO4JscM9LCAmCDCxp_MfLvN4QdB+xWsS-FijbjTYQ@mail.gmail.com track_commit_timestamp tracks COMMIT PREPARED in standby server, but not in master server.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwHereDzzzmfxEBYcVQu3oZv6vZcgu1TPeERWbDc+gQ06g@mail.gmail.com The behavior of the standby when track_commit_timestamp is flipped in the master is weird.]<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
** the crash case requires changes to postgres_fdw that are not and presumably never will be in 9.5, so not clear this is a blocker for 9.5<br />
** it might be sufficient to consider join pushdown as unsupported for now when select-for-update is involved<br />
* {{messageLink|55D5473F.2090807@2ndquadrant.com|Hash joins try to allocate too much memory}}<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha2 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqQ3o10SY6NVdU4pjq85GQTN5tbbkq2gnNUh2fBNU3rKyQ@mail.gmail.com pg_receivexlog --if-not-exists plays with pointer dereference], pointed out by Coverity.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [https://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']. (Actually the problem is effective index corruption; see [https://www.postgresql.org/message-id/20150731194524.GB2441@postgresql.org 20150731194524] for details)<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors] - release note patch committed.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c26170668c82eaaf28b6efbf76c5d1c206c27121 Link $(WIN32RES) into single-file modules only when PGFILEDESC is set.]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b8fe12a83622b350dc6849f8bb933bd8a86c1424 Reconcile nodes/*funcs.c]<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/19440.1438917759@sss.pgh.pa.us brin_page_items() is unsafe against cache flushes]<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
** This now appears to have been a [http://www.postgresql.org/message-id/CAN=rtBjFfoNn2vEXSYRu=21GcvmzBxrYygc4pORAuFRPu9ObNA@mail.gmail.com false alarm] caused by local code changes, and perhaps an inconsistent build.<br />
* [http://www.postgresql.org/message-id/CAB7nPqS_kF7vJaQA6qNbcuQnr5B6JBDyxAz5MuXPsB3KtmoBbA@mail.gmail.com commit_ts and its dereferenced pointers]<br />
* [http://www.postgresql.org/message-id/28006.1433903315@sss.pgh.pa.us PL/Python docs still describe pre-9.5 float conversion semantics]<br />
* [http://www.postgresql.org/message-id/CAHGQGwG6YPSvYZHPFxQY+zUe3EN_Xz77FLgTKe5yxXCC44VOTw@mail.gmail.com CancelBackup() and tablespace_map file]<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
** Decision has been taken to make pg_xlog behave as a repository even if it is detected as a soft link. Switched as such by 0e42397.<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6. Fixed as 426746b.<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched to SUSET.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25707PostgreSQL 9.5 Open Items2015-09-03T13:03:03Z<p>Masaofujii: Added new item about the behavior of the standby with track_commit_timestamp</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Additional documentation can be added to explain RETURNING<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Stephen planning on writing docpatch to take care of this<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
** Needs further rebasing following changes to restrictive policies from extensions<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Only item 5 open.<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various issues with EXCLUDED.* targetlist]<br />
** "excluded.* wholerow var" bug still must be addressed, plus [http://www.postgresql.org/message-id/flat/55C07835.3010409@lab.ntt.co.jp report of issue with dropped columns]. Note that there is also a related issue with OID columns (when tables have OIDs). These are now consolidated into one item here because joined-up thinking is required to fix all these superficially different issues at once.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open pg_rewind Issues ===<br />
* [http://www.postgresql.org/message-id/20150728085711.GB20627@msg.df7cb.de pg_rewind tests are unstable]<br />
<br />
=== Open BRIN Issues ===<br />
<br />
* Oversize item computation needs more testing (c.f. ereport(ERROR) calls in brin_getinsertbuffer)<br />
* {{messageLink|CAE2gYzyB39Q9up_-TO6FKhH44pcAM1x6n_Cuj15qKoLoFihUVg@mail.gmail.com|Document the `inclusion` framework}}<br />
<br />
=== Open track_commit_timestamp Issues ===<br />
* [http://www.postgresql.org/message-id/CAHGQGwFuzfO4JscM9LCAmCDCxp_MfLvN4QdB+xWsS-FijbjTYQ@mail.gmail.com track_commit_timestamp tracks COMMIT PREPARED in standby server, but not in master server.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwHereDzzzmfxEBYcVQu3oZv6vZcgu1TPeERWbDc+gQ06g@mail.gmail.com The behavior of the standby when track_commit_timestamp is flipped in the master is weird.]<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
** the crash case requires changes to postgres_fdw that are not and presumably never will be in 9.5, so not clear this is a blocker for 9.5<br />
** it might be sufficient to consider join pushdown as unsupported for now when select-for-update is involved<br />
* {{messageLink|55D5473F.2090807@2ndquadrant.com|Hash joins try to allocate too much memory}}<br />
* [http://www.postgresql.org/message-id/CAHGQGwG6YPSvYZHPFxQY+zUe3EN_Xz77FLgTKe5yxXCC44VOTw@mail.gmail.com CancelBackup() and tablespace_map file]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha2 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqQ3o10SY6NVdU4pjq85GQTN5tbbkq2gnNUh2fBNU3rKyQ@mail.gmail.com pg_receivexlog --if-not-exists plays with pointer dereference], pointed out by Coverity.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [https://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']. (Actually the problem is effective index corruption; see [https://www.postgresql.org/message-id/20150731194524.GB2441@postgresql.org 20150731194524] for details)<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors] - release note patch committed.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c26170668c82eaaf28b6efbf76c5d1c206c27121 Link $(WIN32RES) into single-file modules only when PGFILEDESC is set.]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b8fe12a83622b350dc6849f8bb933bd8a86c1424 Reconcile nodes/*funcs.c]<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/19440.1438917759@sss.pgh.pa.us brin_page_items() is unsafe against cache flushes]<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
** This now appears to have been a [http://www.postgresql.org/message-id/CAN=rtBjFfoNn2vEXSYRu=21GcvmzBxrYygc4pORAuFRPu9ObNA@mail.gmail.com false alarm] caused by local code changes, and perhaps an inconsistent build.<br />
* [http://www.postgresql.org/message-id/CAB7nPqS_kF7vJaQA6qNbcuQnr5B6JBDyxAz5MuXPsB3KtmoBbA@mail.gmail.com commit_ts and its dereferenced pointers]<br />
* [http://www.postgresql.org/message-id/28006.1433903315@sss.pgh.pa.us PL/Python docs still describe pre-9.5 float conversion semantics]<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
** Decision has been taken to make pg_xlog behave as a repository even if it is detected as a soft link. Switched as such by 0e42397.<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6. Fixed as 426746b.<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched to SUSET.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25706PostgreSQL 9.5 Open Items2015-09-03T12:42:08Z<p>Masaofujii: Add open item about CancelBackup() and tablespace_map.</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Additional documentation can be added to explain RETURNING<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Stephen planning on writing docpatch to take care of this<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
** Needs further rebasing following changes to restrictive policies from extensions<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Only item 5 open.<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various issues with EXCLUDED.* targetlist]<br />
** "excluded.* wholerow var" bug still must be addressed, plus [http://www.postgresql.org/message-id/flat/55C07835.3010409@lab.ntt.co.jp report of issue with dropped columns]. Note that there is also a related issue with OID columns (when tables have OIDs). These are now consolidated into one item here because joined-up thinking is required to fix all these superficially different issues at once.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open pg_rewind Issues ===<br />
* [http://www.postgresql.org/message-id/20150728085711.GB20627@msg.df7cb.de pg_rewind tests are unstable]<br />
<br />
=== Open BRIN Issues ===<br />
<br />
* Oversize item computation needs more testing (c.f. ereport(ERROR) calls in brin_getinsertbuffer)<br />
* {{messageLink|CAE2gYzyB39Q9up_-TO6FKhH44pcAM1x6n_Cuj15qKoLoFihUVg@mail.gmail.com|Document the `inclusion` framework}}<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
** the crash case requires changes to postgres_fdw that are not and presumably never will be in 9.5, so not clear this is a blocker for 9.5<br />
** it might be sufficient to consider join pushdown as unsupported for now when select-for-update is involved<br />
* {{messageLink|55D5473F.2090807@2ndquadrant.com|Hash joins try to allocate too much memory}}<br />
* [http://www.postgresql.org/message-id/CAHGQGwFuzfO4JscM9LCAmCDCxp_MfLvN4QdB+xWsS-FijbjTYQ@mail.gmail.com track_commit_timestamp tracks COMMIT PREPARED in standby server, but not in master server.]<br />
* [http://www.postgresql.org/message-id/CAHGQGwG6YPSvYZHPFxQY+zUe3EN_Xz77FLgTKe5yxXCC44VOTw@mail.gmail.com CancelBackup() and tablespace_map file]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha2 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqQ3o10SY6NVdU4pjq85GQTN5tbbkq2gnNUh2fBNU3rKyQ@mail.gmail.com pg_receivexlog --if-not-exists plays with pointer dereference], pointed out by Coverity.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [https://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']. (Actually the problem is effective index corruption; see [https://www.postgresql.org/message-id/20150731194524.GB2441@postgresql.org 20150731194524] for details)<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors] - release note patch committed.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c26170668c82eaaf28b6efbf76c5d1c206c27121 Link $(WIN32RES) into single-file modules only when PGFILEDESC is set.]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b8fe12a83622b350dc6849f8bb933bd8a86c1424 Reconcile nodes/*funcs.c]<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/19440.1438917759@sss.pgh.pa.us brin_page_items() is unsafe against cache flushes]<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
** This now appears to have been a [http://www.postgresql.org/message-id/CAN=rtBjFfoNn2vEXSYRu=21GcvmzBxrYygc4pORAuFRPu9ObNA@mail.gmail.com false alarm] caused by local code changes, and perhaps an inconsistent build.<br />
* [http://www.postgresql.org/message-id/CAB7nPqS_kF7vJaQA6qNbcuQnr5B6JBDyxAz5MuXPsB3KtmoBbA@mail.gmail.com commit_ts and its dereferenced pointers]<br />
* [http://www.postgresql.org/message-id/28006.1433903315@sss.pgh.pa.us PL/Python docs still describe pre-9.5 float conversion semantics]<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
** Decision has been taken to make pg_xlog behave as a repository even if it is detected as a soft link. Switched as such by 0e42397.<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6. Fixed as 426746b.<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched to SUSET.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25704PostgreSQL 9.5 Open Items2015-09-02T14:14:05Z<p>Masaofujii: /* Other Open Issues */ Added new open item about track_commit_timestamp</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Additional documentation can be added to explain RETURNING<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Stephen planning on writing docpatch to take care of this<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
** Needs further rebasing following changes to restrictive policies from extensions<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Only item 5 open.<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various issues with EXCLUDED.* targetlist]<br />
** "excluded.* wholerow var" bug still must be addressed, plus [http://www.postgresql.org/message-id/flat/55C07835.3010409@lab.ntt.co.jp report of issue with dropped columns]. Note that there is also a related issue with OID columns (when tables have OIDs). These are now consolidated into one item here because joined-up thinking is required to fix all these superficially different issues at once.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open pg_rewind Issues ===<br />
* [http://www.postgresql.org/message-id/20150728085711.GB20627@msg.df7cb.de pg_rewind tests are unstable]<br />
<br />
=== Open BRIN Issues ===<br />
<br />
* Oversize item computation needs more testing (c.f. ereport(ERROR) calls in brin_getinsertbuffer)<br />
* {{messageLink|CAE2gYzyB39Q9up_-TO6FKhH44pcAM1x6n_Cuj15qKoLoFihUVg@mail.gmail.com|Document the `inclusion` framework}}<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
** the crash case requires changes to postgres_fdw that are not and presumably never will be in 9.5, so not clear this is a blocker for 9.5<br />
** it might be sufficient to consider join pushdown as unsupported for now when select-for-update is involved<br />
* {{messageLink|55D5473F.2090807@2ndquadrant.com|Hash joins try to allocate too much memory}}<br />
* [http://www.postgresql.org/message-id/CAHGQGwFuzfO4JscM9LCAmCDCxp_MfLvN4QdB+xWsS-FijbjTYQ@mail.gmail.com track_commit_timestamp tracks COMMIT PREPARED in standby server, but not in master server.]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha2 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqQ3o10SY6NVdU4pjq85GQTN5tbbkq2gnNUh2fBNU3rKyQ@mail.gmail.com pg_receivexlog --if-not-exists plays with pointer dereference], pointed out by Coverity.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [https://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']. (Actually the problem is effective index corruption; see [https://www.postgresql.org/message-id/20150731194524.GB2441@postgresql.org 20150731194524] for details)<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors] - release note patch committed.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c26170668c82eaaf28b6efbf76c5d1c206c27121 Link $(WIN32RES) into single-file modules only when PGFILEDESC is set.]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b8fe12a83622b350dc6849f8bb933bd8a86c1424 Reconcile nodes/*funcs.c]<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/19440.1438917759@sss.pgh.pa.us brin_page_items() is unsafe against cache flushes]<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
** This now appears to have been a [http://www.postgresql.org/message-id/CAN=rtBjFfoNn2vEXSYRu=21GcvmzBxrYygc4pORAuFRPu9ObNA@mail.gmail.com false alarm] caused by local code changes, and perhaps an inconsistent build.<br />
* [http://www.postgresql.org/message-id/CAB7nPqS_kF7vJaQA6qNbcuQnr5B6JBDyxAz5MuXPsB3KtmoBbA@mail.gmail.com commit_ts and its dereferenced pointers]<br />
* [http://www.postgresql.org/message-id/28006.1433903315@sss.pgh.pa.us PL/Python docs still describe pre-9.5 float conversion semantics]<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
** Decision has been taken to make pg_xlog behave as a repository even if it is detected as a soft link. Switched as such by 0e42397.<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6. Fixed as 426746b.<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched to SUSET.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25532PostgreSQL 9.5 Open Items2015-08-03T14:37:02Z<p>Masaofujii: Committed the patch "Ignore tablespace_map file when backup_label is not present"</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
** The last discussion ended [http://www.postgresql.org/message-id/20150611214724.GP26667@tamriel.snowman.net here], which pointed out that it doesn't make sense to try and limit the rows returned based on the SELECT policy because those rows have already been transformed by the statement and might now pass whatever SELECT policy is defined.<br />
** Additional documentation can be added to explain RETURNING<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** Stephen planning on writing docpatch to take care of this<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring.]<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCXXedKjZCwrkXd6hixx6_YS11XiB62Uybsno-D_nfw8Uw@mail.gmail.com posted a rebased patch] on July 30th.<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Only item 5 open.<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors]<br />
** Patch for release notes [http://www.postgresql.org/message-id/CAM3SWZTZ7kJu0fgkxb-FON2tFeGZaeB4=ydGAMP6k7uwkKcS7w@mail.gmail.com posted]<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various fairly minor bugfixes should be committed - 1 remaining from original 3]<br />
** Only "excluded.* wholerow var" bug remains. These fix all known UPSERT bugs as of June 6th.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open Issues Related to Various Write-Ahead Logging Changes in 9.5 ===<br />
<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched as SUSET (post 9.5 alpha1).<br />
<br />
=== Open pg_rewind Issues === <br />
<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
<br />
=== Open BRIN Issues ===<br />
* [http://www.postgresql.org/message-id/20150723204810.GY5596@postgresql.org An all-zeros page might get added to FSM and not initialized]<br />
* [http://www.postgresql.org/message-id/185774103.1833212.1437507758024.JavaMail.yahoo@mail.yahoo.com BRIN regression test fails with default_transaction_isolation = 'repeatable read']<br />
** It is the only regression test that fails at that isolation level, and should be fixed for that reason alone.<br />
** The error message mentions an internal C function name not involved in the problem.<br />
** It fails because a simple VACUUM of a table with a BRIN index can fail, which doesn't seem acceptable.<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
* [http://www.postgresql.org/message-id/CAEZATCUNO34g4pdx3nvW_qf0FDQ=R9oB8J5Cz6KA9GqzXZxtNQ@mail.gmail.com 9.5 release notes item for change to LEAKPROOF semantics]<br />
** This is not just part of RLS - it affects existing users of SB views, and whether or not they need to mark their functions as LEAKPROOF.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CABP8UDS4jf4t6hjNF_g=4e=X=BA_EC2P+AL+Q4y5ESU2E4-Uag@mail.gmail.com Missing reference to TransformRelationId and OCLASS_TRANSFORM in object_classes]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
* Fix AIX build ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=0689cfc 0689cfc], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bcd7c41 bcd7c41], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7193436 7193436])<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/CAEzk6fdVan-rUr5Le2BfNfKncniMdyk4vyVZYnKX_TBJu34Zdw@mail.gmail.com crash with plpgsql caused by CAST]. Test case available.<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Patch [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b26e3d660df51a088d14c3c2cfce5990c13c1195 committed].<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c1ca3a19df376bcbb6d651d15b9a4ffcaa377ff1 Issue with ON CONFLICT DO UPDATE assignment expressions containing indirection]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=159cff58cf3b565be3c17901698a74238e9e23f8 Check the relevant index element in ON CONFLICT unique index inference]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQFqCDXX_R9qde3bjmzXVvuYnnXgTf-u5K3oAqk0VbG0Q@mail.gmail.com XLOG reader facility leaks memory when decoding records], nodes in recovery can fail with OOM after recovering many records.<br />
** Actually not that critical, the problem is in XLogReaderFree which should control a bit more blocks to be freed.<br />
** [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=beebb259d2a994cd2021a1506b7af1716b16f476 patch committed]<br />
* [http://www.postgresql.org/message-id/CAB7nPqSnxBNwNGa0h2zS=3zOh7MdgzbwD_79oij3qc90r3ZO8A@mail.gmail.com Memory leaks of pg_rewind], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=d7fd22a38ff48372c6813983317fc8d1e07fcf87 patch committed]<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure], [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d5cb31c9a17bad8bbc587c09404b2aa1e6c3aac patch committed]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
** Items 1 - 4, 6, 7 fixed/committed/pushed.<br />
* [http://www.postgresql.org/message-id/CAEZATCV2myP6+6OFGNtE=DPe9g0JdwqgU87iAEz=DpV9MgmkQg@mail.gmail.com Suggested improvement/clarification for CREATE FUNCTION docs]<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
*** Joe extracted this part of the overall patch and committed it [http://www.postgresql.org/message-id/E1ZKqrK-0006oz-Ub@gemulon.postgresql.org here]<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
* [http://www.postgresql.org/message-id/20646.1437919632@sss.pgh.pa.us A NULL search key causes segfault]<br />
* [http://www.postgresql.org/message-id/20150727050002.GF1504258@tornado.leadboat.com spgist recovery assertion failure]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=e6ea46c Revert most 9.5 changes to pre-9.5 vcregress.pl tests.]<br />
* [http://www.postgresql.org/message-id/CAA4eK1JNhY6UhH5VQXDWvGYHd3VGyBDT+wqbyvH6BrXEZufotg@mail.gmail.com Ignore tablespace_map file when backup_label is not present]<br />
** Decision whether the error level should be LOG or WARNING is under discussion.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25456PostgreSQL 9.5 Open Items2015-07-14T13:06:41Z<p>Masaofujii: Add TABLESAMPLE open item</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** no responses to Peter's original post<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Dean agrees this is a bug and [http://www.postgresql.org/message-id/CAEZATCXibt_DtzkeHRTS5z-64XfkStKybp=tHMb+TX8n-KOCXg@mail.gmail.com suggests how to fix it] -- his patch fixing the issue needs to be reviewed + committed<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com posted a patch] on June 1st; Stephen indicated he would review it, but no followups on the thread yet<br />
* [http://www.postgresql.org/message-id/flat/20150703070721.GA844443@tornado.leadboat.com copy.c handling for RLS is insecure]<br />
* [http://www.postgresql.org/message-id/20150703170308.GB844443@tornado.leadboat.com more RLS oversights]<br />
* [http://www.postgresql.org/message-id/1436691547878-5857659.post@n5.nabble.com pg_stats leaks information on relations with RLS enabled]<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors]<br />
** Patch for release notes [http://www.postgresql.org/message-id/CAM3SWZTZ7kJu0fgkxb-FON2tFeGZaeB4=ydGAMP6k7uwkKcS7w@mail.gmail.com posted]<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various fairly minor bugfixes should be committed - 3 in all]<br />
** These fix all known UPSERT bugs as of June 6th.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open Issues Related to Various Write-Ahead Logging Changes in 9.5 ===<br />
<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
** Parameter has been switched as SUSET (post 9.5 alpha1).<br />
<br />
=== Open pg_rewind Issues === <br />
<br />
* pg_rewind fails when pg_xlog is defined as a soft link in PGDATA.<br />
** Heikki has mentioned one solution: ignore the content on pg_xlog. We may as well consider later a new option to allow the user to set up a soft link with pg_rewind after a rewind.<br />
** Michael has mentioned another solution: use an implementation of pg_readlink and fetch its content from source to target. This needs as well to modify pg_stat_file such as lstat() is used instead of stat() to detect if a path is a soft link (or junction point on Windows) or not. Perhaps this solution is not worth the backward-incompatibility issues as stat() reports the information of the linked target when meeting up with a soft link/junction point.<br />
<br />
=== Open TABLESAMPLE Issues ===<br />
* [http://www.postgresql.org/message-id/12048.1436646520@sss.pgh.pa.us TABLESAMPLE feature needs a lot of work]<br />
* [http://www.postgresql.org/message-id/9871.1436716927@sss.pgh.pa.us TABLESAMPLE doesn't actually satisfy the SQL spec, does it?]<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
* [http://www.postgresql.org/message-id/flat/20150520192157.GE5885@postgresql.org atomics code has portability issues]<br />
** buildfarm member anole, at least, is still not happy as of 2015-06-28<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6.<br />
* [http://www.postgresql.org/message-id/5592DB35.2060401@iki.fi Deadlock in LWLock]<br />
** interaction between LWLockWaitForVar and the introduction of atomic locking.<br />
* [http://www.postgresql.org/message-id/20150707165212.1188.60819@wrigleys.postgresql.org Crash in planner code with 9.5 alpha 1]<br />
** Report mentions that a query on pg_stat_activity when using pg_hero leads to a crash of server.<br />
** Some tests and analysis (playing with extended query protocol, pghero itself and analysis of planner code by Tom) are though showing up that the back trace and information provided do not show enough information to have a reproducible test case yet. And attempts to reproduce the failure with pgbench failed as of now.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
* [http://www.postgresql.org/message-id/flat/20150704003636.GA856928@tornado.leadboat.com Revoke support for strxfrm() implementations that write past the specified array length.]<br />
* [http://www.postgresql.org/message-id/20150704224041.GA898636@tornado.leadboat.com Finish XLC atomics implementation.]<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea). Fixed by generalizing the missing_ok logic in system file functions present in core. <br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
** Fix done by making sampler recall again pg_erand48 when finding out 0.0. Idea by Tom.<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]. Heikki and Robert have agreed that pg_rewind should fail in this case. Hence users should remove such files from PGDATA before performing a rewind.<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_derived_databases&diff=25442PostgreSQL derived databases2015-07-10T02:46:35Z<p>Masaofujii: Add GresCube as PostgreSQL derived databases</p>
<hr />
<div>A list of PostgreSQL derived forks and rebranded distributions in alphabetical order.<br />
<br />
{| align="center" border="1" cellspacing="0" {{Prettytable}}<br />
|-<br />
!{{Hl2}} |Name<br />
!{{Hl2}} |Vendor<br />
!{{Hl2}} |License<br />
!{{Hl2}} |Availability<br />
!{{Hl2}} |Notes<br />
|-<br />
|Aster Data<br />
|Teradata<br />
|Proprietary<br />
|2005-....<br />
|PostgreSQL + Map/Reduce<br />
|-<br />
|BDR<br />
|2ndQuadrant<br />
|BSD<br />
|2014-<br />
|PostgreSQL Multi Master, contributed actively back to Core PG<br />
|-<br />
|Bizgres<br />
|Greenplum<br />
|BSD<br />
|2005-2007<br />
|PostgreSQL + BI features<br />
|-<br />
|CitusDB<br />
|Citus Data<br />
|Proprietary<br />
|2012-<br />
|Sharding and replication across many servers with MPP [https://www.citusdata.com/citus-products/citusdb-software]<br />
|-<br />
|Cybercluster<br />
|Cybertec<br />
|BSD<br />
|2007-2010<br />
|Clustering (pgCluster fork)<br />
|-<br />
|Greenplum Database <br />
|Greenplum<br />
|proprietary<br />
|2005-....<br />
|PostgreSQL + BI features (formerly known as "Bizgres MPP")<br />
|-<br />
|EnterpriseDB Advanced Server<br />
|EnterpriseDB<br />
|proprietary<br />
|2008-....<br />
|PostgreSQL + Oracle compatibility<br />
|-<br />
|EnterpriseDB Postgres Plus<br />
|EnterpriseDB<br />
|open-source (varies)<br />
|2008-....<br />
|PostgreSQL re-distribution<br />
|-<br />
|ExtenDB<br />
|ExtenDB<br />
|Proprietary<br />
|2003-2007<br />
|PostgreSQL + BI Features [http://www.stormdb.com/community/stado?destination=node%2F8]<br />
|-<br />
|FUJITSU Enterprise Postgres<br />
|Fujitsu<br />
|proprietary<br />
|2006-....<br />
|Full PostgreSQL compatibility with additional functionality [http://www.fujitsu.com/global/products/software/middleware/opensource/postgres/]<br />
|-<br />
|GresCube<br />
|NTT DATA<br />
|Proprietary<br />
|2012-....<br />
|Database appliance solution based on PostgreSQL [http://opensol.jp.nttdata.com/solutions/grescube/]<br />
|-<br />
|GridSQL<br />
|EnterpriseDB<br />
|GPL<br />
|2007-2010<br />
|PostgreSQL + BI Features (formerly ExtenDB) [http://www.stormdb.com/community/stado?destination=node%2F8]<br />
|-<br />
|Great Bridge PostgreSQL<br />
|Great Bridge LLC<br />
|BSD<br />
|1999-2001<br />
|PostgreSQL re-distribution<br />
|-<br />
|HadoopDB<br />
|Yale University<br />
|Apache License V2.0<br />
|2009-....<br />
|PostgreSQL + shared-nothing cluster + Hadoop [http://db.cs.yale.edu/hadoopdb/hadoopdb.html]<br />
|-<br />
|[http://hadapt.com/ Hadapt]<br />
|Teradata<br />
|Proprietary<br />
|2011-....<br />
|HadoopDB fork<br />
|-<br />
|Mammoth<br />
|Command Prompt<br />
|BSD<br />
|2005-2010<br />
|PostgreSQL + proprietary replication + extensions<br />
|-<br />
|Netezza<br />
|IBM<br />
|proprietary<br />
|2002-....<br />
|Appliance based on PostgreSQL SQL engine<br />
|-<br />
|NuSphere UltraSQL<br />
|NuSphere<br />
|proprietary<br />
|2002-2003<br />
|Native Win32 port of PostgreSQL<br />
|-<br />
|ParAccel<br />
|Actian<br />
|proprietary<br />
|2005-....<br />
|PostgreSQL + BI features<br />
|-<br />
|Pervasive PostgreSQL<br />
|Pervasive<br />
|BSD<br />
|2005-2006<br />
|PostgreSQL re-distribution<br />
|-<br />
|pgCluster<br />
|SRA<br />
|BSD<br />
|2002-2005<br />
|Clustering (Share Nothing)<br />
|-<br />
|pgCluster-II<br />
|SRA<br />
|BSD<br />
|2006-2007<br />
|Clustering (Shared Disk)<br />
|-<br />
|pgPool-II<br />
|pgPool GDG<br />
|BSD<br />
|2006-....<br />
|Clustering (Connection Pooling / Replication / Load-Balancing)<br />
|-<br />
|pipelineDB<br />
|PipelineDB<br />
|GPL v3<br />
|2015-....<br />
|Streaming SQL<br />
|-<br />
|PostgresForest<br />
|NTT DATA<br />
|BSD<br />
|2006-2010<br />
|Clustering / PostgresForest is a fork of the JDBC driver, not from the backend code.<br />
|-<br />
|Postgres Plus<br />
|EnterpriseDB<br />
|OSS<br />
|2008-....<br />
|PostgreSQL + contrib + apps + drivers <br />
|-<br />
|Postgres Plus Advanced Server<br />
|EnterpriseDB<br />
|proprietary<br />
|2008-....<br />
|Postgres + Oracle compatibility + apps, formally EnterpriseDB AS<br />
|-<br />
|Postgres-R<br />
|PGDG<br />
|BSD<br />
|2006-2010<br />
|Clustering<br />
|-<br />
|[http://postgres-x2.github.io/ Postgres-X2]<br />
|PGX2DG<br />
|BSD<br />
|2015-<br />
|Clustering (formerly Postgres-XC)<br />
|-<br />
|Postgres-XC<br />
|PGXCDG<br />
|BSD<br />
|2010-2013<br />
|Clustering [http://postgresxc.wikia.com/wiki/Postgres-XC_Wiki]<br />
|-<br />
|Postgres-XL<br />
|PGXLDG<br />
|BSD<br />
|2014-....<br />
|Clustering<br />
|-<br />
|PowerGres<br />
|SRA OSS<br />
|proprietary<br />
|2003-....<br />
|Native Win32 port of PostgreSQL and Linux RPM<br />
|-<br />
|PowerGres Plus<br />
|SRA OSS<br />
|proprietary<br />
|2003-....<br />
|PostgreSQL + custom storage engine, redundant WAL, encrypted database [http://powergres.sraoss.co.jp/s/ja/product/Plus.php]<br />
|-<br />
|PostgreSQL for Solaris<br />
|Sun<br />
|TPL<br />
|2006-2009<br />
|PostgreSQL re-distribution<br />
|-<br />
|RecDB<br />
|umn.edu<br />
|BSD<br />
|2013-....<br />
|Recommendation Engine [http://www-users.cs.umn.edu/~sarwat/RecDB/]<br />
|-<br />
|Red Hat Database<br />
|Red Hat<br />
|BSD<br />
|2002-2003<br />
|PostgreSQL re-distribution<br />
|-<br />
|Red Shift<br />
|Amazon<br />
|Private/Cloud-based <br />
|2013-....<br />
|Data Warehouse on AWS (based on ParACCEL)<br />
|-<br />
|Stado<br />
|Stado GDG<br />
|GPL<br />
|2011-2011<br />
|PostgreSQL + BI Features (fork of GridSQL) [https://wiki.postgresql.org/wiki/Stado]<br />
|-<br />
|TelegraphCQ<br />
|UC Berkeley<br />
|BSD<br />
|2000-2008<br />
|Data Stream oriented fork of PostgreSQL<br />
|-<br />
|TruCQ<br />
|Truviso<br />
|proprietary<br />
|2008-2012<br />
|Fork of TelegraphCQ<br />
|-<br />
|Vertica<br />
|HP<br />
|proprietary<br />
|2005-....<br />
| Column-oriented DataWarehouse (created by Stonebraker),<br />may only be forking the psql client library.<br />
|-<br />
|Yahoo! Everest<br />
|Yahoo!<br />
|private<br />
|2008-....<br />
|multi-petabyte database / MPP [http://fr.scribd.com/doc/3159239/70-EverestPGCon-RT]<br />
|}<br />
<br />
== Related documents ==<br />
<br />
* https://en.wikipedia.org/wiki/Template:Timeline_PostgreSQL<br />
* https://github.com/rafaelma/postgresql-timeline<br />
* http://de.slideshare.net/pgconf/elephant-roads-a-tour-of-postgres-forks<br />
* https://github.com/daamien/artwork/tree/master/inkscape/PostgreSQL_timeline<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Derivative Products|!]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25406PostgreSQL 9.5 Open Items2015-07-03T03:27:33Z<p>Masaofujii: /* Open INSERT .. ON CONFLICT Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** no responses to Peter's original post<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Dean agrees this is a bug and [http://www.postgresql.org/message-id/CAEZATCXibt_DtzkeHRTS5z-64XfkStKybp=tHMb+TX8n-KOCXg@mail.gmail.com suggests how to fix it] -- his patch fixing the issue needs to be reviewed + committed<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com posted a patch] on June 1st; Stephen indicated he would review it, but no followups on the thread yet<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors]<br />
** Patch for release notes [http://www.postgresql.org/message-id/CAM3SWZTZ7kJu0fgkxb-FON2tFeGZaeB4=ydGAMP6k7uwkKcS7w@mail.gmail.com posted]<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various fairly minor bugfixes should be committed - 3 in all]<br />
** These fix all known UPSERT bugs as of June 6th.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
* [http://www.postgresql.org/message-id/CAHGQGwFUCWwSU7dtc2aRdRk73ztyr_jY5cPOyts+K8xKJ92X4Q@mail.gmail.com UPSERT on partition]<br />
** The consensus is to treat the problem as a limitation and document it.<br />
<br />
=== Open Issues Related to Various Write-Ahead Logging Changes in 9.5 ===<br />
<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
<br />
=== Open pg_rewind Issues === <br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea).<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]<br />
<br />
=== TABLESAMPLE ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
* [http://www.postgresql.org/message-id/flat/20150520192157.GE5885@postgresql.org atomics code has portability issues]<br />
** buildfarm member anole, at least, is still not happy as of 2015-06-28<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25405PostgreSQL 9.5 Open Items2015-07-03T03:23:59Z<p>Masaofujii: </p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** no responses to Peter's original post<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Dean agrees this is a bug and [http://www.postgresql.org/message-id/CAEZATCXibt_DtzkeHRTS5z-64XfkStKybp=tHMb+TX8n-KOCXg@mail.gmail.com suggests how to fix it] -- his patch fixing the issue needs to be reviewed + committed<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com posted a patch] on June 1st; Stephen indicated he would review it, but no followups on the thread yet<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors]<br />
** Patch for release notes [http://www.postgresql.org/message-id/CAM3SWZTZ7kJu0fgkxb-FON2tFeGZaeB4=ydGAMP6k7uwkKcS7w@mail.gmail.com posted]<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various fairly minor bugfixes should be committed - 3 in all]<br />
** These fix all known UPSERT bugs as of June 6th.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
<br />
=== Open Issues Related to Various Write-Ahead Logging Changes in 9.5 ===<br />
<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
<br />
=== Open pg_rewind Issues === <br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea).<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]<br />
<br />
=== TABLESAMPLE ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
* [http://www.postgresql.org/message-id/flat/20150520192157.GE5885@postgresql.org atomics code has portability issues]<br />
** buildfarm member anole, at least, is still not happy as of 2015-06-28<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=25374PostgreSQL 9.5 Open Items2015-07-01T03:42:37Z<p>Masaofujii: Add new open item about .paritial WAL file</p>
<hr />
<div>== Open Issues ==<br />
<br />
=== Open Row-Level Security Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** lots of discussion of what the behavior should be, but no patches yet.<br />
* [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** no responses to Peter's original post<br />
* [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** Dean agrees this is a bug and [http://www.postgresql.org/message-id/CAEZATCXibt_DtzkeHRTS5z-64XfkStKybp=tHMb+TX8n-KOCXg@mail.gmail.com suggests how to fix it] -- his patch fixing the issue needs to be reviewed + committed<br />
* [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
** Dean [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com posted a patch] on June 1st; Stephen indicated he would review it, but no followups on the thread yet<br />
<br />
=== Open INSERT .. ON CONFLICT Issues ===<br />
<br />
* [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors]<br />
** Patch for release notes [http://www.postgresql.org/message-id/CAM3SWZTZ7kJu0fgkxb-FON2tFeGZaeB4=ydGAMP6k7uwkKcS7w@mail.gmail.com posted]<br />
* [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various fairly minor bugfixes should be committed - 3 in all]<br />
** These fix all known UPSERT bugs as of June 6th.<br />
* [http://www.postgresql.org/message-id/CAM3SWZTpWo-guh7bZ3xXU9W=QuUHmhLGE2_GO7anGhCOaYg=7A@mail.gmail.com Refactoring speculative insertion with unique indexes a little]<br />
** Feels like the contract that the executor has with speculative insertion + amcanunique AMs should be made explicit, and be documented under [http://www.postgresql.org/docs/devel/static/index-unique-checks.html "51.5. Index Uniqueness Checks"].<br />
<br />
=== Open Issues Related to Various Write-Ahead Logging Changes in 9.5 ===<br />
<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
* [http://www.postgresql.org/message-id/CAHGQGwGxMKnVHGgTfiig2Bt_2djec0in3-DLJmtg7+nEiidFdQ@mail.gmail.com WAL-related tools and .partial WAL file]<br />
** WAL-related tools, i.e., pg_archivecleanup, pg_resetxlog and pg_xlogdump don't seem to properly handle .paritial WAL file.<br />
<br />
=== Open pg_rewind Issues === <br />
<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
** Window triggering failure cannot be reduced to zero, but significantly reduced by scanning files still present in source server with pg_stat_file and a if_not_exists mode (just an idea).<br />
** [http://www.postgresql.org/message-id/CAB7nPqT=nPzXseCyrJ-yvKvE-Q+vC42Cc1VvGcdsEiWb0AZL1w@mail.gmail.com Similar issue with xlogtemp files], can be fixed by ignoring them in process_remote_files().<br />
* [http://www.postgresql.org/message-id/CAB7nPqQYVuG=1npOi8cpbKrOr+Uj2JNeOBJrVqGTJ30kanH1Dg@mail.gmail.com pg_rewind failure when target path contains non-writable files]<br />
<br />
=== TABLESAMPLE ===<br />
<br />
* [http://www.postgresql.org/message-id/CAB7nPqTL0YYPgGt00gV8mw+23U4ki8yXUKV0mfji3YVpAqR8sA@mail.gmail.com Potential log(0) and division by 0 in ANALYZE and TABLESAMPLE]<br />
** partial patch from Michael Paquier is attached to the thread, but Michael says it doesn't cover everything<br />
** [http://www.postgresql.org/message-id/5592CE94.1000208@2ndquadrant.com Correct fix by Petr Jelinek]<br />
<br />
=== Other Open Issues ===<br />
<br />
* DDL deparsing testing module should have detected that transforms were not supported, but it failed to notice that<br />
** Whack it until it does.<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
** this is not a 9.5 regression, although it is a bug<br />
* [http://www.postgresql.org/message-id/CAM3SWZSyWA+g9ygnRrYkvgmnu82fP1b=2wxLBPOWoOgZG83pPA@mail.gmail.com Final jsonb semantics patch, concerning adding negative subscripting everywhere]<br />
** Patch also concerns adding additional minor input sanitization<br />
* [http://www.postgresql.org/message-id/20150622151138.GA6415@localhost PGXS "check" target forcing an install]<br />
** alternative patches from Michael Paquier and Robert Haas, need to pick one (or something else)<br />
* [http://www.postgresql.org/message-id/558A18B3.9050201@lab.ntt.co.jp Foreign join pushdown vs EvalPlanQual]<br />
** server crash; no patch yet<br />
* [http://www.postgresql.org/message-id/flat/20150520192157.GE5885@postgresql.org atomics code has portability issues]<br />
** buildfarm member anole, at least, is still not happy as of 2015-06-28<br />
* [http://www.postgresql.org/message-id/20150624144148.GQ4797@alap3.anarazel.de Removal of SSL renegotiation code], perhaps not directly an issue with 9.5, but we may want to get a good outcome here instead of waiting 1 extra year with 9.6.<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved after 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1xUSStjv+YYiFRBpr6p7C-Brngxm8-OMpkDqvLVa3qkKw@mail.gmail.com PANIC in GIN code] (the second issue, with metapage-update record)<br />
* [http://www.postgresql.org/message-id/CAM3SWZQgLSAYP1wYUaGfFvFd2HXOes7sLsjw0gjOKKCexZsHZw@mail.gmail.com Trivial bug in bttext_abbrev_convert()]<br />
<br />
=== resolved before 9.5alpha1 ===<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=5ca611841bcd37c7ee8448c46c8398ef8d8edcc4 commit])<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
** No more failures, so far anyway. -rhaas, 2015-06-26<br />
* [http://www.postgresql.org/message-id/CAFj8pRAfUx2C7tYAwzeUewFj=AgQOjFHTw4bypfC_e5gjFBAyA@mail.gmail.com less log level for success dynamic background workers for 9.5] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=91118f1a59f2038f072552fdbb98e01363e30b59 commit])<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7abc68597436da1475b4d9b08f4fa9f3c5ed6185 commit])<br />
** [http://www.postgresql.org/message-id/CAHGQGwFv-LUQGcwHs3j33io3CXvNRO2CXn19hqR8rzJHsC0moQ@mail.gmail.com committed by Fujii Masao]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths] ([http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f15f74a44f68f9cb3a644786d3c732a5eeb237a commit])<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
** Alvaro [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=ad89a5d115b3b4025f3c135f95f722e7e4becf13 committed] part of this and, as of 2015-06-22, [http://www.postgresql.org/message-id/20150621192520.GG133018@postgresql.org says he will look at the rest next]<br />
** [http://git.postgresql.org/pg/commitdiff/7d60b2af34842ae89b1abdd31fb5d303bd43c514 second commit]<br />
* [http://www.postgresql.org/message-id/CAMkU=1xyoT4Dz9t6ijsodjOgJaGD-rLad0WW7Vynw4-Zjqyogw@mail.gmail.com PANIC in GIN code]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/28927.1435335457@sss.pgh.pa.us pg_file_settings patch needs some rework]<br />
** current implementation blocks a fix for a 9.4.1 regression concerning unwanted complaints about multiple entries for PGC_POSTMASTER variables<br />
* [http://www.postgresql.org/message-id/29550.1435422769@sss.pgh.pa.us pg_file_settings view does not work properly on Windows]<br />
<br />
== Issues That Don't Need To Be Fixed ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
** seems like this is OK, unless more people weigh in and say it isn't.<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
** per [http://www.postgresql.org/message-id/20150605155120.GA30287@alap3.anarazel.de this post from Andres], the remaining issue here is not 9.5 material<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=25005PgCon 2015 Developer Unconference2015-06-13T18:24:37Z<p>Masaofujii: /* Topics */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Christopher Browne<br />
* Joe Conway<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Magnus Hagander<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Tatsuo Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Yugo Nagata<br />
* Jim Nasby<br />
* Dave Page<br />
* Paul Ramsey<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Rod Taylor<br />
* Tomas Vondra<br />
* Jan Wieck (arrive tuesday evening)<br />
* Chris Winters<br />
* Nat Wyatt<br />
* Naoya Anzai (arrive tuesday evening)<br />
* David Steele (arrive tuesday evening)<br />
* Ingmar Alting<br />
* Mehmet Emin KARAKAŞ<br />
* Yasin TATAR<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|Picture!<br />
|Open<br />
|<br />
|All!<br />
|All!<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas, David Steele, Rod Taylor, Jim Nasby, Chris Winters, Nat Wyatt, Noah Misch, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas, Chris Browne, Josh Berkus, Ingmar Alting, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, Simon Riggs, Robert Haas, David Steele, Rod Taylor, Chris Browne, Jim Nasby, Josh Berkus, Chris Winters, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat, Ahsan Hadi<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas, David Steele, Chris Browne, Jim Nasby, Josh Berkus, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas, Jim Nasby, Josh Berkus, Chris Winters, Ingmar Alting<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas, David Steele, Rod Taylor, Chris Browne, Jim Nasby, Chris Winters, Nat Wyatt, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas, Jim Nasby, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs, Rod Taylor, Jim Nasby, Josh Berkus, Nat Wyatt<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus, Rod Taylor, Jim Nasby<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs, Nat Wyatt<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund, Jim Nasby, Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
| David Steele, Jim Nasby, Josh Berkus, Nat Wyatt, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|Audit Logging<br />
|Open<br />
|<br />
| David Steele<br />
| Josh Berkus, Nat Wyatt, Masao Fujii<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pg_shard v2.0 and Lessons Learned from NoSQL Databases ]]<br />
|Open<br />
|<br />
| Ozgun Erdogan, Marco Slot <br />
| Josh Berkus, Jim Nasby, Josh Berkus, Chris Winters<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Audit Logging ==<br />
<br />
Audit logging is an important part of a RDBMS for many users and applications. Discuss how best to incorporate audit logging into PostgreSQL and what must be included at a minimum to make the feature viable. <br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Meeting&diff=24973PgCon 2015 Developer Meeting2015-06-12T17:09:59Z<p>Masaofujii: /* RSVPs */</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 16 June, 2015 at the University of Ottawa, prior to pgCon 2015. In order to keep the numbers manageable, this meeting is by '''invitation only'''. Unfortunately it is quite possible that we've overlooked important individuals during the planning of the event - if you feel you fall into this category and would like to attend, please contact Dave Page (dpage@pgadmin.org).<br />
<br />
Please note that the attendee numbers have been kept low in order to keep the meeting more productive. Invitations have been sent only to developers that have been highly active on the database server over the 9.5 release cycle. We have not invited any contributors based on their contributions to related projects, or seniority in regional user groups or sponsoring companies.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Changes from Previous Developer Meetings ==<br />
<br />
Note that the goals for this year's "Developer Meeting" have shifted to account for the Unconference which is being held at pgCon immediately following the Developer meeting and lasting for 1.5 days (Tuesday afternoon and all day Wednesday). This year, the "Developer meeting" will be focused on non-technical issues such as timing/schedule, policies, procedures, and [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems], be they technical or non-technical in nature. The nature of such Wicked problems is that they require a sufficient number of interested individuals to make progress and generally involve both technical and non-technical issues (trade-off decisions, no clear true or false answer, no way to test if a given solution is correct, etc). The Unconference will be focused on technical discussions and design. If you have any questions regarding the nature of the Developer meeting, please contact Dave Page (dpage@pgadmin.org).<br />
<br />
== Meeting Goals ==<br />
<br />
* Define the schedule for the 9.6 release cycle<br />
* Address any proposed timing, policy, or procedure issues<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
<br />
== Time & Location ==<br />
<br />
The meeting will be from 9:00AM to 12PM at the University of Ottawa. We will update this wiki with the specific room information once we have it.<br />
<br />
Note that this meeting is intentionally shorter this year. This is due to the Unconference being held at pgCon.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Jeff Davis<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Magnus Hagander<br />
* Álvaro Herrera<br />
* Amit Kapila<br />
* Tom Lane<br />
* Heikki Linnakangas<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Dave Page<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:15<br />
|Welcome and introductions<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:45 - 11:00<br />
|Coffee break<br />
|<br />
<br />
|-<br />
|11:00 - 11:45<br />
|9.6 Schedule<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|11:45 - 12:00<br />
|Any other business<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:00<br />
|Finish<br />
|<br />
|}<br />
<br />
= Meeting Notes =<br />
<br />
== Attendees ==</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24972PgCon 2015 Developer Unconference2015-06-12T17:09:28Z<p>Masaofujii: /* RSVPs */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Tomas Vondra<br />
* Tatsuo Ishii<br />
* Yugo Nagata<br />
* Jan Wieck (arrive tuesday evening)<br />
* Joe Conway<br />
* Naoya Anzai (arrive tuesday evening)<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, SImon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[Bi Directional Replication & Logical Decoding|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
|<br />
<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=24927PostgreSQL 9.5 Open Items2015-06-11T01:10:14Z<p>Masaofujii: Add issue about pg_rewind to Open Items</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1z4kq-8+GPounmqqtyRJ-4+Uxf0-2NAzY=Mtq73+g6FrQ@mail.gmail.com docs about max_wal_size in recovery do not match behavior]<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
* [http://www.postgresql.org/message-id/flat/555673D0.5090406@dunslane.net brin regression test intermittent failures]<br />
** This is probably fixed as of 4-June, but it would be a good idea to watch chipmunk for a week or two before declaring the issue closed.<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes]<br />
* Row-level security<br />
** [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
** [http://www.postgresql.org/message-id/CAM3SWZScG+S17vwT+E82o=aNrjqar6=kCoAnGf+vw=n4PaAgCw@mail.gmail.com Arguable RLS security bug, EvalPlanQual() paranoia]<br />
** [http://www.postgresql.org/message-id/CAM3SWZRvgL3Ti87etps1L38eba=jNFS9e1vLS7xN6p7vhwOeHg@mail.gmail.com RLS fails to work with UPDATE ... WHERE CURRENT OF]<br />
** [http://www.postgresql.org/message-id/CAEZATCVE7hdtfZGCJN-oevVaWBtBGG8-fBCh9VhDBHuZrsWY5w@mail.gmail.com Dean's latest round of RLS refactoring. Includes notable bugfix.]<br />
*** DML queries with additional non-target (FROM/USING) relations cared about UPDATE/DELETE applicable policies, not SELECT applicable policies. This is clearly a bug.<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** the testing module should have detected this automatically. Whack it until it does<br />
** [http://www.postgresql.org/message-id/CAB7nPqT2SZ39N_wH+WK8JGPKO3LCyWQiLoxgcgq_UyPJNc8hSg@mail.gmail.com Patch for support of CREATE/DROP TRANSFORM in DDL deparsing, one bug found with DROP TRANSFORM]<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KEFoTJ8kRxsTid=ZRx8Rd593B+86-GCDDey5s2Mqqw_g@mail.gmail.com Remove symlinks in pg_tblspc during archive recovery and error for non-symlink paths]<br />
* ON CONFLICT DO UPDATE/NOTHING<br />
** [http://www.postgresql.org/message-id/CAM3SWZRY92akby8LuibtA=A9-QY5yFrQ+_+m2QvsbdQkbVce5g@mail.gmail.com 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors]<br />
** [http://www.postgresql.org/message-id/flat/CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com#CAM3SWZS8RPvA=KFxADZWw3wAHnnbxMxDzkEC6fNaFc7zSm411w@mail.gmail.com Various fairly minor bugfixes should be committed - 3 in all. These fix all known UPSERT bugs as of June 6th.]<br />
* [http://www.postgresql.org/message-id/CAB7nPqRSe8GTDJy74Yp3cVONx5Xx9H6Xr82sTDHbNa_b1q8zCw@mail.gmail.com Memory leak with XLogFileCopy since de768844 (WAL file with .partial)]<br />
* [http://www.postgresql.org/message-id/20150120152819.GC24381@alap3.anarazel.de basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe]<br />
* [http://www.postgresql.org/message-id/CAM3SWZQFSWMi2aVi-Lun_JBYh-RfHQ3-0fm8TXpW8OLc+v8ZnQ@mail.gmail.com Further issues with jsonb semantics, documentation]<br />
** It's clear that at least <i>some</i> further tweaks are required.<br />
* [http://www.postgresql.org/message-id/CAB7nPqReR+MUupGA5wd9tywdhhgHkREnY9OEJemMxkd2zzrvQw@mail.gmail.com All information of pg_stat_ssl visible to every users]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEdsNgeNZo+GyrzZtjW_TkC=XC6XxrjuAZ7=X_cj1aHHg@mail.gmail.com pg_rewind failure by file deletion in source server]<br />
<br />
== Resolved Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail] (pg_audit has been reverted)<br />
* [http://www.postgresql.org/message-id/7758.1433610350@sss.pgh.pa.us intermittent "cache lookup failed for access method 403" failure at session start]<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=24726PostgreSQL 9.5 Open Items2015-05-22T01:23:48Z<p>Masaofujii: /* Open Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1z4kq-8+GPounmqqtyRJ-4+Uxf0-2NAzY=Mtq73+g6FrQ@mail.gmail.com docs about max_wal_size in recovery do not match behavior]<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
* [http://www.postgresql.org/message-id/20150508223227.GP2523@alvh.no-ip.org "unaddressable bytes" in BRIN]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** the testing module should have detected this automatically. Whack it until it does<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
* [http://www.postgresql.org/message-id/CAMkU=1x-djpi6Cjq_xbFCzVgEpnAO1J-=fzePhcfq2UwGnoSng@mail.gmail.com max_wal_size and restartpoints]<br />
<br />
== Resolved Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=24718PostgreSQL 9.5 Open Items2015-05-21T05:29:36Z<p>Masaofujii: /* Open Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1z4kq-8+GPounmqqtyRJ-4+Uxf0-2NAzY=Mtq73+g6FrQ@mail.gmail.com docs about max_wal_size in recovery do not match behavior]<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
* [http://www.postgresql.org/message-id/20150508223227.GP2523@alvh.no-ip.org "unaddressable bytes" in BRIN]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
* DDL deparsing does not support CREATE/ALTER TRANSFORM<br />
** the testing module should have detected this automatically. Whack it until it does<br />
* [http://www.postgresql.org/message-id/20150315132707.GB19792@alap3.anarazel.de recovery_target_action = pause & hot_standby = off]<br />
<br />
== Resolved Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=24697PostgreSQL 9.5 Open Items2015-05-19T13:27:02Z<p>Masaofujii: /* Open Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1z4kq-8+GPounmqqtyRJ-4+Uxf0-2NAzY=Mtq73+g6FrQ@mail.gmail.com docs about max_wal_size in recovery do not match behavior]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
* [http://www.postgresql.org/message-id/20150508223227.GP2523@alvh.no-ip.org "unaddressable bytes" in BRIN]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail]<br />
* [http://www.postgresql.org/message-id/CAHGQGwEqWD=yNQE+ZojbpoxyWT3xLK52-V_q9S+XOfCKJd5egA@mail.gmail.com CREATE POLICY and RETURNING]<br />
<br />
== Resolved Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.5_Open_Items&diff=24696PostgreSQL 9.5 Open Items2015-05-19T13:17:57Z<p>Masaofujii: /* Open Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/CAMkU=1z4kq-8+GPounmqqtyRJ-4+Uxf0-2NAzY=Mtq73+g6FrQ@mail.gmail.com docs about max_wal_size in recovery do not match behavior]<br />
* [http://www.postgresql.org/message-id/87d24y7xwa.fsf@news-spur.riddles.org.uk Re: collations in shared catalogs?]<br />
* [http://www.postgresql.org/message-id/55269915.1000309@iki.fi FPW compression leaks information] Make wal_compression SUSET and document potential security risks?<br />
* [http://www.postgresql.org/message-id/20150508223227.GP2523@alvh.no-ip.org "unaddressable bytes" in BRIN]<br />
* [http://www.postgresql.org/message-id/9A28C8860F777E439AA12E8AEA7694F8010DC708@BPXM15GP.gisp.nec.co.jp custom-join has no way to construct Plan nodes of child Path nodes]<br />
* [http://www.postgresql.org/message-id/CAHGQGwE0XfGJPL6NUjaPcO6sZyiXEE4eCBR96XYkzL-N0mD8uA@mail.gmail.com CREATE EXTENSION pg_audit can fail]<br />
<br />
== Resolved Issues ==<br />
<br />
* [http://www.postgresql.org/message-id/546A16EF.9070005@vmware.com BRIN page type identifier] BRIN special space needs reshuffling<br />
* [http://www.postgresql.org/message-id/CAEZATCXHb+tv8YYo4=XRoBzCOywTrM4cncqR57D4ZM7WdFomiQ@mail.gmail.com proposal: searching in array function - array_position] array_offset(s) do not consider arrays not starting from 1<br />
* [http://www.postgresql.org/message-id/CAB7nPqQSdx7coHk0D6G=mkJntGYjXPDw+PWisKKSsAeZFTskvg@mail.gmail.com Assertion failure when streaming logical changes] (crash in walsender replaying from a logical decoding slot)<br />
* [http://www.postgresql.org/message-id/20141128205453.GA1737@alvh.no-ip.org no test programs in contrib] fix src/test/modules to work on MSVC<br />
* [http://www.postgresql.org/message-id/CAG6W84JA8bhrEzDvv6UaTOyZGBPwDnQb7ZqJRm6wtJdn+mBY9Q@mail.gmail.com Improve GB18030 <-> UTF8 encoding conversions]<br />
* [http://www.postgresql.org/message-id/20150312.213812.115476889.horiguchi.kyotaro@lab.ntt.co.jp alter user/role CURRENT_USER] CURRENT_USER needs some fixes<br />
* [http://www.postgresql.org/message-id/55427924.9090806@dunslane.net transforms vs CLOBBER_CACHE_ALWAYS]<br />
<br />
[[Category:PostgreSQL_9.5]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=23123PostgreSQL 9.4 Open Items2014-09-09T14:21:20Z<p>Masaofujii: </p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://www.postgresql.org/message-id/537A449F.1020108@gmx.net vacuumdb --all --analyze-in-stages - wrong order]<br />
* [http://www.postgresql.org/message-id/10107.1405625479@sss.pgh.pa.us TAP tests still have some pretty severe problems]<br />
* [http://www.postgresql.org/message-id/1407548062.13736.7.camel@vanquo.pezone.net psql output change in 9.4]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
* [http://www.postgresql.org/message-id/27839.1407467863@sss.pgh.pa.us jsonb data format doesn't work well with toast compression]<br />
* [http://www.postgresql.org/message-id/20140904051356.2926.42797@wrigleys.postgresql.org log_statement and ALTER SYSTEM]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KLn1SmgVtd=5emAbQxrrPVeEdTBUU94E-rEPMwxWVL+A@mail.gmail.com prohibit data_directory to be set via Alter System]<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/53B51F88.8030801@catalyst.net.nz ALTER SYSTEM has issues with PGC_POSTMASTER parameters]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/20140815211138.2543.16364@wrigleys.postgresql.org Broken pg_operator info for JSONB operators]<br />
* [http://www.postgresql.org/message-id/CAA4eK1LgjvsB7cj09LTD5ZEPQS7T48CJWt7w_BZ0kNvg5pFm4A@mail.gmail.com option -T in pg_basebackup doesn't work on windows]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=23000PostgreSQL 9.4 Open Items2014-08-13T01:42:43Z<p>Masaofujii: </p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/537A449F.1020108@gmx.net vacuumdb --all --analyze-in-stages - wrong order]<br />
* [http://www.postgresql.org/message-id/10107.1405625479@sss.pgh.pa.us TAP tests still have some pretty severe problems]<br />
* [http://www.postgresql.org/message-id/CAA4eK1LgjvsB7cj09LTD5ZEPQS7T48CJWt7w_BZ0kNvg5pFm4A@mail.gmail.com option -T in pg_basebackup doesn't work on windows]<br />
* [http://www.postgresql.org/message-id/1407548062.13736.7.camel@vanquo.pezone.net psql output change in 9.4]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KLn1SmgVtd=5emAbQxrrPVeEdTBUU94E-rEPMwxWVL+A@mail.gmail.com prohibit data_directory to be set via Alter System]<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/53B51F88.8030801@catalyst.net.nz ALTER SYSTEM has issues with PGC_POSTMASTER parameters]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22967PostgreSQL 9.4 Open Items2014-08-07T13:36:45Z<p>Masaofujii: The commit which had caused the assertion error with LWLOCK_STATS enabled was reverted.</p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/537A449F.1020108@gmx.net vacuumdb --all --analyze-in-stages - wrong order]<br />
* [http://www.postgresql.org/message-id/10107.1405625479@sss.pgh.pa.us TAP tests still have some pretty severe problems]<br />
* [http://www.postgresql.org/message-id/CAA4eK1LgjvsB7cj09LTD5ZEPQS7T48CJWt7w_BZ0kNvg5pFm4A@mail.gmail.com option -T in pg_basebackup doesn't work on windows]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KLn1SmgVtd=5emAbQxrrPVeEdTBUU94E-rEPMwxWVL+A@mail.gmail.com prohibit data_directory to be set via Alter System]<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/53B51F88.8030801@catalyst.net.nz ALTER SYSTEM has issues with PGC_POSTMASTER parameters]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22958PostgreSQL 9.4 Open Items2014-08-06T17:13:22Z<p>Masaofujii: Fixed the ALTER SYSTEM issue with PGC_POSTMASTER parameters.</p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
* [http://www.postgresql.org/message-id/537A449F.1020108@gmx.net vacuumdb --all --analyze-in-stages - wrong order]<br />
* [http://www.postgresql.org/message-id/10107.1405625479@sss.pgh.pa.us TAP tests still have some pretty severe problems]<br />
* [http://www.postgresql.org/message-id/CAA4eK1LgjvsB7cj09LTD5ZEPQS7T48CJWt7w_BZ0kNvg5pFm4A@mail.gmail.com option -T in pg_basebackup doesn't work on windows]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KLn1SmgVtd=5emAbQxrrPVeEdTBUU94E-rEPMwxWVL+A@mail.gmail.com prohibit data_directory to be set via Alter System]<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/53B51F88.8030801@catalyst.net.nz ALTER SYSTEM has issues with PGC_POSTMASTER parameters]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22956PostgreSQL 9.4 Open Items2014-08-05T02:05:58Z<p>Masaofujii: Add new open issue related to pg_basebackup on Windows.</p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
* [http://www.postgresql.org/message-id/537A449F.1020108@gmx.net vacuumdb --all --analyze-in-stages - wrong order]<br />
* [http://www.postgresql.org/message-id/53B51F88.8030801@catalyst.net.nz ALTER SYSTEM has issues with PGC_POSTMASTER parameters]<br />
* [http://www.postgresql.org/message-id/10107.1405625479@sss.pgh.pa.us TAP tests still have some pretty severe problems]<br />
* [http://www.postgresql.org/message-id/CAA4eK1LgjvsB7cj09LTD5ZEPQS7T48CJWt7w_BZ0kNvg5pFm4A@mail.gmail.com option -T in pg_basebackup doesn't work on windows]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KLn1SmgVtd=5emAbQxrrPVeEdTBUU94E-rEPMwxWVL+A@mail.gmail.com prohibit data_directory to be set via Alter System]<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22754PostgreSQL 9.4 Open Items2014-06-23T10:52:17Z<p>Masaofujii: Disallowed ALTER SYSTEM command to set data_directory</p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
* [http://www.postgresql.org/message-id/537A449F.1020108@gmx.net vacuumdb --all --analyze-in-stages - wrong order]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/CAA4eK1KLn1SmgVtd=5emAbQxrrPVeEdTBUU94E-rEPMwxWVL+A@mail.gmail.com prohibit data_directory to be set via Alter System]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22419PostgreSQL 9.4 Open Items2014-05-21T14:05:01Z<p>Masaofujii: /* Open Issues */ add assersion failure bug with LWLOCK_STATS</p>
<hr />
<div>== Open Issues ==<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
* [http://www.postgresql.org/message-id/BLU0-SMTP69FCBF7F3A6FCDA70FAE74DC520@phx.gbl assertion when palloc'ing within a critical section]<br />
* [http://www.postgresql.org/message-id/537B0C2E.6090706@gmail.com HEAD crashes with assertion and LWLOCK_STATS enabled]<br />
<br />
== Resolved Issues ==<br />
* [http://www.postgresql.org/message-id/20140320143839.GR6899@eldon.alvh.no-ip.org Immediate shutdown no longer removes backup_label if backup is in progress]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://www.postgresql.org/message-id/CAMkU=1yE4YyCC00W_GcNoOZ4X2qxF7x5DUAR_kMt-Ta=YPyFPQ@mail.gmail.com autovacuum scheduling starvation and frenzy]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=22321PostgreSQL 9.4 Open Items2014-05-12T16:22:04Z<p>Masaofujii: Immdiate shutdown removes backup_label, and no one wanted to revert this behavior per discussion.</p>
<hr />
<div><br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots/xloginsert_locks GUC] - Not yet!!<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
* [http://www.postgresql.org/message-id/5358A38F.50808@2ndquadrant.com Bgworker process exit code definitions aren't very sane]<br />
* [http://archives.postgresql.org/message-id/20140430161754.GG30324@alap3.anarazel.de the client program tests don't work in vpath builds]<br />
* [http://www.postgresql.org/message-id/CAFj8pRA5VCT44W8XcoKkGQ0MDPV7UQ7B7FBaHiuaXZemOtaB+w@mail.gmail.com psql output in expanded+wrapped mode has some issues ]<br />
<br />
[[Category:PostgreSQL_9.4]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.4_Open_Items&diff=21958PostgreSQL 9.4 Open Items2014-03-18T11:46:09Z<p>Masaofujii: Add new TODO item related to GIN</p>
<hr />
<div>* [http://www.postgresql.org/message-id/E1UKCHE-0000pd-OO@gemulon.postgresql.org Adjust error message about version incompatibility to say "9.3 or above" ]<br />
* [http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9a20a9b21baa819df1760b36f3c36f25d11fc27b] Consider removing xloginsert_slots GUC<br />
* [http://www.postgresql.org/message-id/20130808165031.GA23572@momjian.us Remove non-fast recovery code as it is no longer needed and cannot be accesssed]<br />
* [http://www.postgresql.org/message-id/CAA-aLv7tYHDzMGg4HtDZh0RQZjJc2v2weJ-Obm4yvkw6ePe9Qw@mail.gmail.com Performance regression when using posix_fallocate on ext4 filesystems]<br />
[[Category:PostgreSQL 9.4]]<br />
* [http://www.postgresql.org/message-id/CA+TgmoYpJntEMkE1zWd+MMEXiOaTpdPpbuNKGvcF5DM_2HJ+zA@mail.gmail.com Revisit default of 4x shared buffers for effective_cache_size]<br />
* [http://www.postgresql.org/message-id/CAB7nPqQJeASxDr0Rt9CJiaf9OnfjoJstyk18iw+oXi-OBO4gYA@mail.gmail.com Remove xloginsert_slots GUC]<br />
* [http://www.postgresql.org/message-id/52E8F035.8080405@vmware.com Add more documentation for huge_tlb_pages]<br />
* GIN fast scan and compression loose ends:<br />
** [http://www.postgresql.org/message-id/53208532.8090005@vmware.com] A few things we might want to fix / rename<br />
** [http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com] Cost estimation needs to be fixed<br />
** [http://www.postgresql.org/message-id/CAHGQGwE3xnytNBY0mnLbQ9+QvgPvL44iEE6bcnsm86eanPWEjg@mail.gmail.com] WAL size needs to be reduced when FASTUPDATE is disabled</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.3_Open_Items&diff=20116PostgreSQL 9.3 Open Items2013-06-10T18:16:01Z<p>Masaofujii: Mark "pg_isready doesn't handle conninfo properly" as resolved.</p>
<hr />
<div>== Project Planning ==<br />
See the [[PostgreSQL 9.3 Development Plan]].<br />
<br />
== Blockers for 9.3 ==<br />
* Improve the {{messageLink|m2zjwxpk8j.fsf@2ndQuadrant.fr|event trigger API documentation?}}<br />
<br />
== Not Blockers for 9.3 ==<br />
<br />
* Consider whether COPY into newly created tables should ALWAYS freeze, perhaps only when checksums enabled - requested by Noah, Robert<br />
<br />
== Meta-Issues ==<br />
<br />
== Resolved Issues ==<br />
* Restructure ProcessUtility to fix event-trigger clobber-cache-always failures<br />
* Agree on the new page checksum algorithm<br />
* Fix planner {{messageLink|6546.1365701142@sss.pgh.pa.us|equivalence-class bugs}}<br />
* pg_ctl's new idempotent option [http://www.postgresql.org/message-id/CAMkU=1zKGzGoDoO=u4MON8h6Q=biRL59PTZvRmR9J7uX0yKoyA@mail.gmail.com broke crash recovery cases]<br />
* [http://www.postgresql.org/message-id/CAHGQGwESOme9HUmUq_jTYi8j++qP2HoZxyqXR=37zuU8tHEOkw@mail.gmail.com VACUUM breaks matview scannability state]<br />
* Do something about {{messageLink|14345.1365001149@sss.pgh.pa.us|unlogged matviews}}<br />
* [http://www.postgresql.org/message-id/CAHGQGwEO1GF3=7LAeyn630+PNjjkC4fnwqx_L_Vyq6Y+OsB5jg@mail.gmail.com Another assertion failure at promotion]<br />
* [http://www.postgresql.org/message-id/CAB7nPqRhuCuuD012GCB_tAAFrixx2WioN_zfXQcvLuRab8DN2g@mail.gmail.com Assertion failure when promoting node by deleting recovery.conf and restart node]<br />
* [http://www.postgresql.org/message-id/CAHGQGwHs3r2k-N7C=vWEk5e-fE7sTGWgZjbkD6X2_s0h+zqoVQ@mail.gmail.com fast promotion and log_checkpoints] - trivial cosmetic issue; not a bug of any kind<br />
* [http://www.postgresql.org/message-id/5188CFFA.3020209@vmware.com Fast promotion failure]<br />
* [http://www.postgresql.org/message-id/12365.1358098148@sss.pgh.pa.us Restore protection against accidentally creating stuff in pg_catalog schema]<br />
** There are a couple of ways to fix that, per thread, but we need to do something.<br />
** As a quick fix, reverted commit a475c603.<br />
* [http://www.postgresql.org/message-id/CAHGQGwH-Zb2obt_GhzMwXEasrB7JWCWH_K9vJXsVP_RmCVRpPg@mail.gmail.com pg_isready doesn't handle conninfo properly]<br />
<br />
== Long-term Issues ==<br />
<br />
<br />
[[Category:PostgreSQL 9.3]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=Committers&diff=20115Committers2013-06-10T16:38:24Z<p>Masaofujii: </p>
<hr />
<div>This is the current list of people with access to push to the git repository with their user names. For technical details on how committing works, see [[Committing with Git]]. Note: This is just a list of people who currently have access to push to git; for information on current and previous contributors, see the [http://www.postgresql.org/community/contributors/ contributor profiles] section of the web site. Note: The names are listed here in order of first commit, oldest first; this isn't intended to imply anything about depth of contribution.<br />
<br />
* Bruce Momjian (momjian)<br />
* Tom Lane (tgl)<br />
* Michael Meskes (meskes)<br />
* Tatsuo Ishii (ishii)<br />
* Peter Eisentraut (petere)<br />
* Teodor Sigaev (teodor)<br />
* Joe Conway (joe)<br />
* Alvaro Herrera (alvherre)<br />
* Andrew Dunstan (adunstan)<br />
* Magnus Hagander (mha)<br />
* Heikki Linnakangas (heikki)<br />
* Robert Haas (rhaas)<br />
* Itagaki Takahiro (itagaki)<br />
* Simon Riggs (sriggs)<br />
* Greg Stark (stark)<br />
* Kevin Grittner (kgrittn)<br />
* Jeff Davis (jdavis)<br />
* Stephen Frost (sfrost)<br />
* Fujii Masao (fujii)<br />
* Noah Misch (noah)<br />
<br />
== Notes on the Commit Log ==<br />
<br />
Hundreds of developers have successfully contributed work to PostgreSQL over more than 20 years, many acting as individuals, though also many representing academic institutions and both user and vendor companies. Both the "Author" and "Committer" fields of such patches will reflect the committer. The actual author of a patch, if different, is generally listed in the commit message; reviewers or others who contributed ideas or otherwise helped with the patch may also be listed. Many patches, in the form in which they are committed, are the work of multiple people: original author or authors, reviewer(s), and/or committer. As a result, no simple analysis of duration or depth of contribution over time is possible from the commit log. The project operates a system of careful peer review and even committers have their work checked by other committers and the community as a whole. <br />
<br />
== New Committers ==<br />
<br />
There is no defined process for how new committers are selected. Typically, candidates will have sent many good patches over a longer period of time. Then, existing committers or the core team will propose making the person a committer. The final approval is done by the core team.<br />
<br />
<br />
[[Category:Community]]</div>Masaofujiihttps://wiki.postgresql.org/index.php?title=PostgreSQL_9.3_Open_Items&diff=20033PostgreSQL 9.3 Open Items2013-06-02T17:21:19Z<p>Masaofujii: </p>
<hr />
<div>== Project Planning ==<br />
See the [[PostgreSQL 9.3 Development Plan]].<br />
<br />
== Blockers for 9.3 ==<br />
* [http://www.postgresql.org/message-id/12365.1358098148@sss.pgh.pa.us Restore protection against accidentally creating stuff in pg_catalog schema]<br />
** There are a couple of ways to fix that, per thread, but we need to do something.<br />
* Improve the {{messageLink|m2zjwxpk8j.fsf@2ndQuadrant.fr|event trigger API documentation?}}<br />
* [http://www.postgresql.org/message-id/5188CFFA.3020209@vmware.com Fast promotion failure] - doesn't appear to be an issue with fast promotion, not sure where though...<br />
* [http://www.postgresql.org/message-id/CAHGQGwH-Zb2obt_GhzMwXEasrB7JWCWH_K9vJXsVP_RmCVRpPg@mail.gmail.com pg_isready doesn't handle conninfo properly]<br />
<br />
== Not Blockers for 9.3 ==<br />
<br />
* Consider whether COPY into newly created tables should ALWAYS freeze, perhaps only when checksums enabled - requested by Noah, Robert<br />
<br />
== Meta-Issues ==<br />
<br />
== Resolved Issues ==<br />
* Restructure ProcessUtility to fix event-trigger clobber-cache-always failures<br />
* Agree on the new page checksum algorithm<br />
* Fix planner {{messageLink|6546.1365701142@sss.pgh.pa.us|equivalence-class bugs}}<br />
* pg_ctl's new idempotent option [http://www.postgresql.org/message-id/CAMkU=1zKGzGoDoO=u4MON8h6Q=biRL59PTZvRmR9J7uX0yKoyA@mail.gmail.com broke crash recovery cases]<br />
* [http://www.postgresql.org/message-id/CAHGQGwESOme9HUmUq_jTYi8j++qP2HoZxyqXR=37zuU8tHEOkw@mail.gmail.com VACUUM breaks matview scannability state]<br />
* Do something about {{messageLink|14345.1365001149@sss.pgh.pa.us|unlogged matviews}}<br />
* [http://www.postgresql.org/message-id/CAHGQGwEO1GF3=7LAeyn630+PNjjkC4fnwqx_L_Vyq6Y+OsB5jg@mail.gmail.com Another assertion failure at promotion]<br />
* [http://www.postgresql.org/message-id/CAB7nPqRhuCuuD012GCB_tAAFrixx2WioN_zfXQcvLuRab8DN2g@mail.gmail.com Assertion failure when promoting node by deleting recovery.conf and restart node]<br />
* [http://www.postgresql.org/message-id/CAHGQGwHs3r2k-N7C=vWEk5e-fE7sTGWgZjbkD6X2_s0h+zqoVQ@mail.gmail.com fast promotion and log_checkpoints] - trivial cosmetic issue; not a bug of any kind<br />
<br />
== Long-term Issues ==<br />
<br />
<br />
[[Category:PostgreSQL 9.3]]</div>Masaofujii