Newer
Older
<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
<sect1 id="release-9-2-17">
<title>Release 9.2.17</title>
<note>
<title>Release Date</title>
<simpara>2016-05-12</simpara>
</note>
<para>
This release contains a variety of fixes from 9.2.16.
For information about new features in the 9.2 major release, see
<xref linkend="release-9-2">.
</para>
<sect2>
<title>Migration to Version 9.2.17</title>
<para>
A dump/restore is not required for those running 9.2.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.2.11,
see <xref linkend="release-9-2-11">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Clear the OpenSSL error queue before OpenSSL calls, rather than
assuming it's clear already; and make sure we leave it clear
afterwards (Peter Geoghegan, Dave Vitek, Peter Eisentraut)
</para>
<para>
This change prevents problems when there are multiple connections
using OpenSSL within a single process and not all the code involved
follows the same rules for when to clear the error queue.
Failures have been reported specifically when a client application
uses SSL connections in <application>libpq</> concurrently with
SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL.
It's possible for similar problems to arise within the server as well,
if an extension module establishes an outgoing SSL connection.
</para>
</listitem>
<listitem>
<para>
Fix <quote>failed to build any <replaceable>N</>-way joins</quote>
planner error with a full join enclosed in the right-hand side of a
left join (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix incorrect handling of equivalence-class tests in multilevel
nestloop plans (Tom Lane)
</para>
<para>
Given a three-or-more-way equivalence class of variables, such
as <literal>X.X = Y.Y = Z.Z</>, it was possible for the planner to omit
some of the tests needed to enforce that all the variables are actually
equal, leading to join rows being output that didn't satisfy
the <literal>WHERE</> clauses. For various reasons, erroneous plans
were seldom selected in practice, so that this bug has gone undetected
for a long time.
</para>
</listitem>
<listitem>
<para>
Fix possible misbehavior of <literal>TH</>, <literal>th</>,
and <literal>Y,YYY</> format codes in <function>to_timestamp()</>
(Tom Lane)
</para>
<para>
These could advance off the end of the input string, causing subsequent
format codes to read garbage.
</para>
</listitem>
<listitem>
<para>
Fix dumping of rules and views in which the <replaceable>array</>
argument of a <literal><replaceable>value</> <replaceable>operator</>
ANY (<replaceable>array</>)</literal> construct is a sub-SELECT
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Make <application>pg_regress</> use a startup timeout from the
<envar>PGCTLTIMEOUT</> environment variable, if that's set (Tom Lane)
</para>
<para>
This is for consistency with a behavior recently added
to <application>pg_ctl</>; it eases automated testing on slow machines.
</para>
</listitem>
<listitem>
<para>
Fix <application>pg_upgrade</> to correctly restore extension
membership for operator families containing only one operator class
(Tom Lane)
</para>
<para>
In such a case, the operator family was restored into the new database,
but it was no longer marked as part of the extension. This had no
immediate ill effects, but would cause later <application>pg_dump</>
runs to emit output that would cause (harmless) errors on restore.
</para>
</listitem>
<listitem>
<para>
Back-port 9.4-era memory-barrier code changes into 9.2 and 9.3 (Tom Lane)
</para>
<para>
These changes were not originally needed in pre-9.4 branches, but we
recently back-patched a fix that expected the barrier code to work
properly. Only IA64 (when using icc), HPPA, and Alpha platforms are
affected.
</para>
</listitem>
<listitem>
<para>
Reduce the number of SysV semaphores used by a build configured with
<option>--disable-spinlocks</> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Rename internal function <function>strtoi()</>
to <function>strtoint()</> to avoid conflict with a NetBSD library
function (Thomas Munro)
</para>
</listitem>
<listitem>
<para>
Fix reporting of errors from <function>bind()</>
and <function>listen()</> system calls on Windows (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Reduce verbosity of compiler output when building with Microsoft Visual
Studio (Christian Ullrich)
</para>
</listitem>
<listitem>
<para>
Avoid possibly-unsafe use of Windows' <function>FormatMessage()</>
function (Christian Ullrich)
</para>
<para>
Use the <literal>FORMAT_MESSAGE_IGNORE_INSERTS</> flag where
appropriate. No live bug is known to exist here, but it seems like a
good idea to be careful.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2016d
for DST law changes in Russia and Venezuela. There are new zone
names <literal>Europe/Kirov</> and <literal>Asia/Tomsk</> to reflect
the fact that these regions now have different time zone histories from
adjacent regions.
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
<sect1 id="release-9-2-16">
<title>Release 9.2.16</title>
<note>
<title>Release Date</title>
<simpara>2016-03-31</simpara>
</note>
<para>
This release contains a variety of fixes from 9.2.15.
For information about new features in the 9.2 major release, see
<xref linkend="release-9-2">.
</para>
<sect2>
<title>Migration to Version 9.2.16</title>
<para>
A dump/restore is not required for those running 9.2.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.2.11,
see <xref linkend="release-9-2-11">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Fix incorrect handling of NULL index entries in
indexed <literal>ROW()</> comparisons (Tom Lane)
</para>
<para>
An index search using a row comparison such as <literal>ROW(a, b) >
ROW('x', 'y')</> would stop upon reaching a NULL entry in
the <structfield>b</> column, ignoring the fact that there might be
non-NULL <structfield>b</> values associated with later values
of <structfield>a</>.
</para>
</listitem>
<listitem>
<para>
Avoid unlikely data-loss scenarios due to renaming files without
adequate <function>fsync()</> calls before and after (Michael Paquier,
Tomas Vondra, Andres Freund)
</para>
</listitem>
<listitem>
<para>
Correctly handle cases where <literal>pg_subtrans</> is close to XID
wraparound during server startup (Jeff Janes)
</para>
</listitem>
<listitem>
<para>
Fix corner-case crash due to trying to free <function>localeconv()</>
output strings more than once (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix parsing of affix files for <literal>ispell</> dictionaries
(Tom Lane)
</para>
<para>
The code could go wrong if the affix file contained any characters
whose byte length changes during case-folding, for
example <literal>I</> in Turkish UTF8 locales.
</para>
</listitem>
<listitem>
<para>
Avoid use of <function>sscanf()</> to parse <literal>ispell</>
dictionary files (Artur Zakirov)
</para>
<para>
This dodges a portability problem on FreeBSD-derived platforms
(including OS X).
</para>
</listitem>
<listitem>
<para>
Avoid a crash on old Windows versions (before 7SP1/2008R2SP1) with an
AVX2-capable CPU and a Postgres build done with Visual Studio 2013
(Christian Ullrich)
</para>
<para>
This is a workaround for a bug in Visual Studio 2013's runtime
library, which Microsoft have stated they will not fix in that
version.
</para>
</listitem>
<listitem>
<para>
Fix <application>psql</>'s tab completion logic to handle multibyte
characters properly (Kyotaro Horiguchi, Robert Haas)
</para>
</listitem>
<listitem>
<para>
Fix <application>psql</>'s tab completion for
<literal>SECURITY LABEL</> (Tom Lane)
</para>
<para>
Pressing TAB after <literal>SECURITY LABEL</> might cause a crash
or offering of inappropriate keywords.
</para>
</listitem>
<listitem>
<para>
Make <application>pg_ctl</> accept a wait timeout from the
<envar>PGCTLTIMEOUT</> environment variable, if none is specified on
the command line (Noah Misch)
</para>
<para>
This eases testing of slower buildfarm members by allowing them
to globally specify a longer-than-normal timeout for postmaster
startup and shutdown.
</para>
</listitem>
<listitem>
<para>
Fix incorrect test for Windows service status
in <application>pg_ctl</> (Manuel Mathar)
</para>
<para>
The previous set of minor releases attempted to
fix <application>pg_ctl</> to properly determine whether to send log
messages to Window's Event Log, but got the test backwards.
</para>
</listitem>
<listitem>
<para>
Fix <application>pgbench</> to correctly handle the combination
of <literal>-C</> and <literal>-M prepared</> options (Tom Lane)
</para>
</listitem>
<listitem>
<para>
In PL/Perl, properly translate empty Postgres arrays into empty Perl
arrays (Alex Hunsaker)
</para>
</listitem>
<listitem>
<para>
Make PL/Python cope with function names that aren't valid Python
identifiers (Jim Nasby)
</para>
</listitem>
<listitem>
<para>
Fix multiple mistakes in the statistics returned
by <filename>contrib/pgstattuple</>'s <function>pgstatindex()</>
function (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Remove dependency on <literal>psed</> in MSVC builds, since it's no
longer provided by core Perl (Michael Paquier, Andrew Dunstan)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2016c
for DST law changes in Azerbaijan, Chile, Haiti, Palestine, and Russia
(Altai, Astrakhan, Kirov, Sakhalin, Ulyanovsk regions), plus
historical corrections for Lithuania, Moldova, and Russia
(Kaliningrad, Samara, Volgograd).
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
<sect1 id="release-9-2-15">
<title>Release 9.2.15</title>
<note>
<title>Release Date</title>
<simpara>2016-02-11</simpara>
</note>
<para>
This release contains a variety of fixes from 9.2.14.
For information about new features in the 9.2 major release, see
<xref linkend="release-9-2">.
</para>
<sect2>
<title>Migration to Version 9.2.15</title>
<para>
A dump/restore is not required for those running 9.2.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.2.11,
see <xref linkend="release-9-2-11">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Fix infinite loops and buffer-overrun problems in regular expressions
(Tom Lane)
</para>
<para>
Very large character ranges in bracket expressions could cause
infinite loops in some cases, and memory overwrites in other cases.
(CVE-2016-0773)
</para>
</listitem>
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
<listitem>
<para>
Perform an immediate shutdown if the <filename>postmaster.pid</> file
is removed (Tom Lane)
</para>
<para>
The postmaster now checks every minute or so
that <filename>postmaster.pid</> is still there and still contains its
own PID. If not, it performs an immediate shutdown, as though it had
received <systemitem>SIGQUIT</>. The main motivation for this change
is to ensure that failed buildfarm runs will get cleaned up without
manual intervention; but it also serves to limit the bad effects if a
DBA forcibly removes <filename>postmaster.pid</> and then starts a new
postmaster.
</para>
</listitem>
<listitem>
<para>
In <literal>SERIALIZABLE</> transaction isolation mode, serialization
anomalies could be missed due to race conditions during insertions
(Kevin Grittner, Thomas Munro)
</para>
</listitem>
<listitem>
<para>
Fix failure to emit appropriate WAL records when doing <literal>ALTER
TABLE ... SET TABLESPACE</> for unlogged relations (Michael Paquier,
Andres Freund)
</para>
<para>
Even though the relation's data is unlogged, the move must be logged or
the relation will be inaccessible after a standby is promoted to master.
</para>
</listitem>
<listitem>
<para>
Fix possible misinitialization of unlogged relations at the end of
crash recovery (Andres Freund, Michael Paquier)
</para>
</listitem>
<listitem>
<para>
Fix <command>ALTER COLUMN TYPE</> to reconstruct inherited check
constraints properly (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix <command>REASSIGN OWNED</> to change ownership of composite types
properly (Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
Fix <command>REASSIGN OWNED</> and <command>ALTER OWNER</> to correctly
update granted-permissions lists when changing owners of data types,
foreign data wrappers, or foreign servers (Bruce Momjian,
Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
Fix <command>REASSIGN OWNED</> to ignore foreign user mappings,
rather than fail (Álvaro Herrera)
</para>
</listitem>
<listitem>
<para>
Add more defenses against bad planner cost estimates for GIN index
scans when the index's internal statistics are very out-of-date
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Make planner cope with hypothetical GIN indexes suggested by an index
advisor plug-in (Julien Rouhaud)
</para>
</listitem>
<listitem>
<para>
Fix dumping of whole-row Vars in <literal>ROW()</>
and <literal>VALUES()</> lists (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix possible internal overflow in <type>numeric</> division
(Dean Rasheed)
</para>
</listitem>
<listitem>
<para>
Fix enforcement of restrictions inside parentheses within regular
expression lookahead constraints (Tom Lane)
</para>
<para>
Lookahead constraints aren't allowed to contain backrefs, and
parentheses within them are always considered non-capturing, according
to the manual. However, the code failed to handle these cases properly
inside a parenthesized subexpression, and would give unexpected
results.
</para>
</listitem>
<listitem>
<para>
Conversion of regular expressions to indexscan bounds could produce
incorrect bounds from regexps containing lookahead constraints
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix regular-expression compiler to handle loops of constraint arcs
(Tom Lane)
</para>
<para>
The code added for CVE-2007-4772 was both incomplete, in that it didn't
handle loops involving more than one state, and incorrect, in that it
could cause assertion failures (though there seem to be no bad
consequences of that in a non-assert build). Multi-state loops would
cause the compiler to run until the query was canceled or it reached
the too-many-states error condition.
</para>
</listitem>
<listitem>
<para>
Improve memory-usage accounting in regular-expression compiler
(Tom Lane)
</para>
<para>
This causes the code to emit <quote>regular expression is too
complex</> errors in some cases that previously used unreasonable
amounts of time and memory.
</para>
</listitem>
<listitem>
<para>
Improve performance of regular-expression compiler (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Make <literal>%h</> and <literal>%r</> escapes
in <varname>log_line_prefix</> work for messages emitted due
to <varname>log_connections</> (Tom Lane)
</para>
<para>
Previously, <literal>%h</>/<literal>%r</> started to work just after a
new session had emitted the <quote>connection received</> log message;
now they work for that message too.
</para>
</listitem>
<listitem>
<para>
On Windows, ensure the shared-memory mapping handle gets closed in
child processes that don't need it (Tom Lane, Amit Kapila)
</para>
<para>
This oversight resulted in failure to recover from crashes
whenever <varname>logging_collector</> is turned on.
</para>
</listitem>
<listitem>
<para>
Fix possible failure to detect socket EOF in non-blocking mode on
Windows (Tom Lane)
</para>
<para>
It's not entirely clear whether this problem can happen in pre-9.5
branches, but if it did, the symptom would be that a walsender process
would wait indefinitely rather than noticing a loss of connection.
</para>
</listitem>
<listitem>
<para>
Avoid leaking a token handle during SSPI authentication
(Christian Ullrich)
</para>
</listitem>
<listitem>
<para>
In <application>psql</>, ensure that <application>libreadline</>'s idea
of the screen size is updated when the terminal window size changes
(Merlin Moncure)
</para>
<para>
Previously, <application>libreadline</> did not notice if the window
was resized during query output, leading to strange behavior during
later input of multiline queries.
</para>
</listitem>
<listitem>
<para>
Fix <application>psql</>'s <literal>\det</> command to interpret its
pattern argument the same way as other <literal>\d</> commands with
potentially schema-qualified patterns do (Reece Hart)
</para>
</listitem>
<listitem>
<para>
Avoid possible crash in <application>psql</>'s <literal>\c</> command
when previous connection was via Unix socket and command specifies a
new hostname and same username (Tom Lane)
</para>
</listitem>
<listitem>
<para>
In <literal>pg_ctl start -w</>, test child process status directly
rather than relying on heuristics (Tom Lane, Michael Paquier)
</para>
<para>
Previously, <application>pg_ctl</> relied on an assumption that the new
postmaster would always create <filename>postmaster.pid</> within five
seconds. But that can fail on heavily-loaded systems,
causing <application>pg_ctl</> to report incorrectly that the
postmaster failed to start.
</para>
<para>
Except on Windows, this change also means that a <literal>pg_ctl start
-w</> done immediately after another such command will now reliably
fail, whereas previously it would report success if done within two
seconds of the first command.
</para>
</listitem>
<listitem>
<para>
In <literal>pg_ctl start -w</>, don't attempt to use a wildcard listen
address to connect to the postmaster (Kondo Yuta)
</para>
<para>
On Windows, <application>pg_ctl</> would fail to detect postmaster
startup if <varname>listen_addresses</> is set to <literal>0.0.0.0</>
or <literal>::</>, because it would try to use that value verbatim as
the address to connect to, which doesn't work. Instead assume
that <literal>127.0.0.1</> or <literal>::1</>, respectively, is the
right thing to use.
</para>
</listitem>
<listitem>
<para>
In <application>pg_ctl</> on Windows, check service status to decide
where to send output, rather than checking if standard output is a
terminal (Michael Paquier)
</para>
</listitem>
<listitem>
<para>
In <application>pg_dump</> and <application>pg_basebackup</>, adopt
the GNU convention for handling tar-archive members exceeding 8GB
(Tom Lane)
</para>
<para>
The POSIX standard for <literal>tar</> file format does not allow
archive member files to exceed 8GB, but most modern implementations
of <application>tar</> support an extension that fixes that. Adopt
this extension so that <application>pg_dump</> with <option>-Ft</> no
longer fails on tables with more than 8GB of data, and so
that <application>pg_basebackup</> can handle files larger than 8GB.
In addition, fix some portability issues that could cause failures for
members between 4GB and 8GB on some platforms. Potentially these
problems could cause unrecoverable data loss due to unreadable backup
files.
</para>
</listitem>
<listitem>
<para>
Fix assorted corner-case bugs in <application>pg_dump</>'s processing
of extension member objects (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Make <application>pg_dump</> mark a view's triggers as needing to be
processed after its rule, to prevent possible failure during
parallel <application>pg_restore</> (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Ensure that relation option values are properly quoted
in <application>pg_dump</> (Kouhei Sutou, Tom Lane)
</para>
<para>
A reloption value that isn't a simple identifier or number could lead
to dump/reload failures due to syntax errors in CREATE statements
issued by <application>pg_dump</>. This is not an issue with any
reloption currently supported by core <productname>PostgreSQL</>, but
extensions could allow reloptions that cause the problem.
</para>
</listitem>
<listitem>
<para>
Fix <application>pg_upgrade</>'s file-copying code to handle errors
properly on Windows (Bruce Momjian)
</para>
</listitem>
<listitem>
<para>
Install guards in <application>pgbench</> against corner-case overflow
conditions during evaluation of script-specified division or modulo
operators (Fabien Coelho, Michael Paquier)
</para>
</listitem>
<listitem>
<para>
Fix failure to localize messages emitted
by <application>pg_receivexlog</> and <application>pg_recvlogical</>
(Ioseph Kim)
</para>
</listitem>
<listitem>
<para>
Avoid dump/reload problems when using both <application>plpython2</>
and <application>plpython3</> (Tom Lane)
</para>
<para>
In principle, both versions of <application>PL/Python</> can be used in
the same database, though not in the same session (because the two
versions of <application>libpython</> cannot safely be used concurrently).
However, <application>pg_restore</> and <application>pg_upgrade</> both
do things that can fall foul of the same-session restriction. Work
around that by changing the timing of the check.
</para>
</listitem>
<listitem>
<para>
Fix <application>PL/Python</> regression tests to pass with Python 3.5
(Peter Eisentraut)
</para>
</listitem>
<listitem>
<para>
Prevent certain <application>PL/Java</> parameters from being set by
non-superusers (Noah Misch)
</para>
<para>
This change mitigates a <application>PL/Java</> security bug
(CVE-2016-0766), which was fixed in <application>PL/Java</> by marking
these parameters as superuser-only. To fix the security hazard for
sites that update <productname>PostgreSQL</> more frequently
than <application>PL/Java</>, make the core code aware of them also.
</para>
</listitem>
<listitem>
<para>
Improve <application>libpq</>'s handling of out-of-memory situations
(Michael Paquier, Amit Kapila, Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
Fix order of arguments
in <application>ecpg</>-generated <literal>typedef</> statements
(Michael Meskes)
</para>
</listitem>
<listitem>
<para>
Use <literal>%g</> not <literal>%f</> format
in <application>ecpg</>'s <function>PGTYPESnumeric_from_double()</>
(Tom Lane)
</para>
</listitem>
<listitem>
<para>
Fix <application>ecpg</>-supplied header files to not contain comments
continued from a preprocessor directive line onto the next line
(Michael Meskes)
</para>
<para>
Such a comment is rejected by <application>ecpg</>. It's not yet clear
whether <application>ecpg</> itself should be changed.
</para>
</listitem>
<listitem>
<para>
Ensure that <filename>contrib/pgcrypto</>'s <function>crypt()</>
function can be interrupted by query cancel (Andreas Karlsson)
</para>
</listitem>
<listitem>
<para>
Accept <application>flex</> versions later than 2.5.x
(Tom Lane, Michael Paquier)
</para>
<para>
Now that flex 2.6.0 has been released, the version checks in our build
scripts needed to be adjusted.
</para>
</listitem>
<listitem>
<para>
Install our <filename>missing</> script where PGXS builds can find it
(Jim Nasby)
</para>
<para>
This allows sane behavior in a PGXS build done on a machine where build
tools such as <application>bison</> are missing.
</para>
</listitem>
<listitem>
<para>
Ensure that <filename>dynloader.h</> is included in the installed
header files in MSVC builds (Bruce Momjian, Michael Paquier)
</para>
</listitem>
<listitem>
<para>
Add variant regression test expected-output file to match behavior of
current <application>libxml2</> (Tom Lane)
</para>
<para>
The fix for <application>libxml2</>'s CVE-2015-7499 causes it not to
output error context reports in some cases where it used to do so.
This seems to be a bug, but we'll probably have to live with it for
some time, so work around it.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2016a for
DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
<sect1 id="release-9-2-14">
<title>Release 9.2.14</title>
<note>
<title>Release Date</title>
<simpara>2015-10-08</simpara>
</note>
<para>
This release contains a variety of fixes from 9.2.13.
For information about new features in the 9.2 major release, see
<xref linkend="release-9-2">.
</para>
<sect2>
<title>Migration to Version 9.2.14</title>
<para>
A dump/restore is not required for those running 9.2.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.2.11,
see <xref linkend="release-9-2-11">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Fix <filename>contrib/pgcrypto</> to detect and report
too-short <function>crypt()</> salts (Josh Kupershmidt)
</para>
<para>
Certain invalid salt arguments crashed the server or disclosed a few
bytes of server memory. We have not ruled out the viability of
attacks that arrange for presence of confidential information in the
disclosed bytes, but they seem unlikely. (CVE-2015-5288)
</para>
</listitem>