@@ -147,10 +147,12 @@ Branch: REL_11_STABLE [1ad521099] 2019-01-24 14:09:56 -0300
147
147
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
148
148
Branch: master [0464fdf07] 2019-01-21 20:08:52 -0300
149
149
Branch: REL_11_STABLE [123cc697a] 2019-01-21 19:59:07 -0300
150
+ Branch: master [cb90de1aa] 2019-02-10 10:00:11 -0300
151
+ Branch: REL_11_STABLE [cc126b45e] 2019-02-10 10:00:11 -0300
150
152
-->
151
153
<para>
152
154
Create or delete foreign key enforcement triggers correctly when
153
- attaching or detaching a partition in a a partitioned table that
155
+ attaching or detaching a partition in a partitioned table that
154
156
has a foreign-key constraint (Amit Langote, Álvaro Herrera)
155
157
</para>
156
158
</listitem>
@@ -241,12 +243,13 @@ Branch: REL_10_STABLE [85efd1a04] 2018-11-19 11:16:28 -0300
241
243
Author: Andres Freund <andres@anarazel.de>
242
244
Branch: master [171e0418b] 2019-02-06 01:09:32 -0800
243
245
Branch: REL_11_STABLE [297d627e0] 2019-02-06 01:09:42 -0800
246
+ Branch: REL_11_STABLE [920311ab1] 2019-02-09 02:44:10 -0800
244
247
-->
245
248
<para>
246
249
Fix possible index corruption when the indexed column has
247
250
a <quote>fast default</quote> (that is, it was added
248
- by <literal>ALTER TABLE ADD COLUMN</literal> with a constant
249
- default value specified, after the table already contained rows)
251
+ by <literal>ALTER TABLE ADD COLUMN</literal> with a constant non-NULL
252
+ default value specified, after the table already contained some rows)
250
253
(Andres Freund)
251
254
</para>
252
255
</listitem>
@@ -291,7 +294,15 @@ Branch: REL_10_STABLE [2e3bd064e] 2018-12-13 06:22:39 +0300
291
294
-->
292
295
<para>
293
296
Avoid deadlock between GIN vacuuming and concurrent index insertions
294
- (Alexander Korotkov, Andrey Borodin and Peter Geoghegan)
297
+ (Alexander Korotkov, Andrey Borodin, Peter Geoghegan)
298
+ </para>
299
+
300
+ <para>
301
+ This change partially reverts a performance improvement, introduced
302
+ in version 10.0, that attempted to reduce the number of index pages
303
+ locked during deletion of a GIN posting tree page. That's now been
304
+ found to lead to deadlocks, so we've removed it pending closer
305
+ analysis.
295
306
</para>
296
307
</listitem>
297
308
@@ -371,8 +382,8 @@ Branch: REL9_5_STABLE [90f1ba7ec] 2019-02-01 10:35:58 +0900
371
382
Branch: REL9_4_STABLE [05d24cf7c] 2019-02-01 10:36:02 +0900
372
383
-->
373
384
<para>
374
- Avoid possibly including garbage in the replica identity field of a
375
- tuple deletion WAL record (Stas Kelvish )
385
+ Avoid possibly writing an incorrect replica identity field in a
386
+ tuple deletion WAL record (Stas Kelvich )
376
387
</para>
377
388
</listitem>
378
389
@@ -464,6 +475,24 @@ Branch: REL_11_STABLE [aee085bc0] 2018-11-27 10:07:43 -0800
464
475
465
476
<listitem>
466
477
<!--
478
+ Author: Andres Freund <andres@anarazel.de>
479
+ Branch: master [5567d12ce] 2019-02-09 01:05:49 -0800
480
+ Branch: REL_11_STABLE [9cf37a527] 2019-02-09 01:05:50 -0800
481
+ Branch: master [3b632a58e] 2019-02-09 01:05:49 -0800
482
+ Branch: REL_11_STABLE [350b0a403] 2019-02-09 01:05:50 -0800
483
+ Branch: master [317ffdfea] 2019-02-09 01:05:49 -0800
484
+ Branch: REL_11_STABLE [6455c6588] 2019-02-09 01:05:50 -0800
485
+ Branch: master [356687bd8] 2019-02-09 01:05:49 -0800
486
+ Branch: REL_11_STABLE [35afccaba] 2019-02-09 01:05:50 -0800
487
+ -->
488
+ <para>
489
+ Fix performance and memory leakage issues in hash-based grouping
490
+ (Andres Freund)
491
+ </para>
492
+ </listitem>
493
+
494
+ <listitem>
495
+ <!--
467
496
Author: Andrew Gierth <rhodiumtoad@postgresql.org>
468
497
Branch: master [d16d45387] 2019-01-17 06:46:10 +0000
469
498
Branch: REL_11_STABLE [e74d8c508] 2019-01-17 06:24:53 +0000
@@ -599,7 +628,7 @@ Branch: REL9_4_STABLE [2abc87953] 2018-11-12 11:19:04 -0500
599
628
-->
600
629
<para>
601
630
Avoid O(N^2) planning time growth when a query contains many
602
- thousands of indexable clauses (Tom Lane)
631
+ thousand indexable clauses (Tom Lane)
603
632
</para>
604
633
</listitem>
605
634
@@ -657,7 +686,7 @@ Branch: REL9_4_STABLE [1d7007671] 2018-12-27 10:17:42 +0900
657
686
658
687
<para>
659
688
This brings <command>TRUNCATE</command> into line with the behavior
660
- of other commands.
689
+ of other commands. Previously, such cases usually ended in failure.
661
690
</para>
662
691
</listitem>
663
692
@@ -893,9 +922,8 @@ Branch: REL_11_STABLE [6b6c64a96] 2018-11-13 17:47:00 +1300
893
922
-->
894
923
<para>
895
924
Fix parsing of space-separated lists of host names in
896
- the <varname>ldapserver</varname> parameter
897
- of <filename>pg_hba.conf</filename> LDAP authentication entries
898
- (Thomas Munro)
925
+ the <varname>ldapserver</varname> parameter of LDAP authentication
926
+ entries in <filename>pg_hba.conf</filename> (Thomas Munro)
899
927
</para>
900
928
</listitem>
901
929
@@ -909,7 +937,7 @@ Branch: REL9_6_STABLE [63d835066] 2018-11-28 14:20:07 +1300
909
937
-->
910
938
<para>
911
939
When making a PAM authentication request, don't set
912
- the <varname>PAM_RHOST</varname> variable if the connection is over
940
+ the <varname>PAM_RHOST</varname> variable if the connection is via
913
941
a Unix socket (Thomas Munro)
914
942
</para>
915
943
@@ -942,7 +970,7 @@ Branch: REL9_4_STABLE [2407d4807] 2018-11-08 17:33:26 -0500
942
970
in the <productname>PostgreSQL</productname> wire protocol
943
971
specification, and it caused some clients to become very confused.
944
972
In released branches, fix this by silently treating such settings as
945
- meaning <literal>ERROR</literal> instead. Release 12 and later will
973
+ meaning <literal>ERROR</literal> instead. Version 12 and later will
946
974
reject those alternatives altogether.
947
975
</para>
948
976
</listitem>
@@ -1045,8 +1073,8 @@ Branch: REL9_4_STABLE [74bfb5388] 2018-11-26 17:32:51 -0500
1045
1073
1046
1074
<para>
1047
1075
Backslash and some other ASCII punctuation characters were not
1048
- rendered correctly, leading to document syntax errors or unexpected
1049
- output.
1076
+ rendered correctly, leading to document syntax errors or wrong
1077
+ characters in the output.
1050
1078
</para>
1051
1079
</listitem>
1052
1080
@@ -1146,6 +1174,24 @@ Branch: REL_11_STABLE [b72b4fafb] 2018-11-13 09:41:34 +0100
1146
1174
1147
1175
<listitem>
1148
1176
<!--
1177
+ Author: Tom Lane <tgl@sss.pgh.pa.us>
1178
+ Branch: master [4dbe19690] 2019-02-09 19:45:38 -0500
1179
+ Branch: REL_11_STABLE [ef9bf3593] 2019-02-09 19:45:38 -0500
1180
+ Branch: REL_10_STABLE [73668c590] 2019-02-09 19:45:38 -0500
1181
+ Branch: REL9_6_STABLE [2b6009e2a] 2019-02-09 19:45:38 -0500
1182
+ Branch: REL9_5_STABLE [2c8332177] 2019-02-09 19:45:38 -0500
1183
+ Branch: REL9_4_STABLE [ed46d0d32] 2019-02-09 19:45:38 -0500
1184
+ -->
1185
+ <para>
1186
+ Avoid null-pointer-dereference crash on some platforms
1187
+ when <application>pg_dump</application>
1188
+ or <application>pg_restore</application> tries to report an error
1189
+ (Tom Lane)
1190
+ </para>
1191
+ </listitem>
1192
+
1193
+ <listitem>
1194
+ <!--
1149
1195
Author: Peter Geoghegan <pg@bowt.ie>
1150
1196
Branch: master [eba775345] 2019-02-06 15:54:19 -0800
1151
1197
Branch: REL_11_STABLE [2f5416666] 2019-02-06 15:54:17 -0800
@@ -1171,7 +1217,7 @@ Branch: REL_11_STABLE [b1894a607] 2018-12-16 14:32:14 -0500
1171
1217
Branch: REL_10_STABLE [34010ac2f] 2018-12-16 14:32:14 -0500
1172
1218
-->
1173
1219
<para>
1174
- Properly disregard <literal>EPIPE </literal> errors if <command>COPY
1220
+ Properly disregard <literal>SIGPIPE </literal> errors if <command>COPY
1175
1221
FROM PROGRAM</command> stops reading the program's output early
1176
1222
(Tom Lane)
1177
1223
</para>
@@ -1203,8 +1249,10 @@ Branch: REL9_4_STABLE [e5a6ae97e] 2018-11-24 21:17:09 +0000
1203
1249
The previous coding did not give the same result as for an
1204
1250
empty <type>hstore</type> value created by a newer version, thus
1205
1251
potentially causing wrong results in hash joins or hash
1206
- aggregation. It might be advisable to reindex any hash indexes
1207
- built on <type>hstore</type> columns.
1252
+ aggregation. It is advisable to reindex any hash indexes
1253
+ built on <type>hstore</type> columns, if the table might contain
1254
+ data that was originally stored as far back as 8.4 and was never
1255
+ dumped/reloaded since then.
1208
1256
</para>
1209
1257
</listitem>
1210
1258
@@ -1325,8 +1373,8 @@ Branch: REL9_4_STABLE [51884fa16] 2019-02-05 10:06:12 -0500
1325
1373
-->
1326
1374
<para>
1327
1375
Fix Perl-coded build scripts to not
1328
- assume <quote><literal>.</literal></quote> is in the search path, as
1329
- recent Perl versions don't include that (Andrew Dunstan)
1376
+ assume <quote><literal>.</literal></quote> is in the search path,
1377
+ since recent Perl versions don't include that (Andrew Dunstan)
1330
1378
</para>
1331
1379
</listitem>
1332
1380
@@ -1347,6 +1395,25 @@ Branch: REL9_4_STABLE [b161ffe31] 2019-01-18 15:06:26 -0500
1347
1395
1348
1396
<listitem>
1349
1397
<!--
1398
+ Author: Tom Lane <tgl@sss.pgh.pa.us>
1399
+ Branch: master [640158386] 2019-02-09 11:41:09 -0500
1400
+ Branch: REL_11_STABLE [027b5a300] 2019-02-09 11:41:09 -0500
1401
+ Branch: REL_10_STABLE [dc0eb137f] 2019-02-09 11:41:09 -0500
1402
+ Branch: REL9_6_STABLE [6257f525a] 2019-02-09 11:41:09 -0500
1403
+ -->
1404
+ <para>
1405
+ Relocate call of <literal>set_rel_pathlist_hook</literal> so that
1406
+ extensions can use it to supply partial paths for parallel queries
1407
+ (KaiGai Kohei)
1408
+ </para>
1409
+
1410
+ <para>
1411
+ This is not expected to affect existing use-cases.
1412
+ </para>
1413
+ </listitem>
1414
+
1415
+ <listitem>
1416
+ <!--
1350
1417
NOTE this is already in 11.1 notes, but not 10.x !!!!
1351
1418
Author: Tom Lane <tgl@sss.pgh.pa.us>
1352
1419
Branch: master [003c68a3b] 2018-11-06 13:25:24 -0500
0 commit comments