Skip to content

Commit 23ba370

Browse files
committed
Merged with 9.5.3 state of REL9_5_STABLE
2 parents af691cd + ba37ac2 commit 23ba370

File tree

62 files changed

+9839
-7618
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

62 files changed

+9839
-7618
lines changed

configure

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
#! /bin/sh
22
# Guess values for system-dependent variables and create Makefiles.
3-
# Generated by GNU Autoconf 2.69 for PostgreSQL 9.5.2.
3+
# Generated by GNU Autoconf 2.69 for PostgreSQL 9.5.3.
44
#
5-
# Report bugs to <bugs@postgrespro.ru>.
5+
# Report bugs to <pgsql-bugs@postgresql.org>.
66
#
77
#
88
# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
@@ -270,10 +270,10 @@ fi
270270
$as_echo "$0: be upgraded to zsh 4.3.4 or later."
271271
else
272272
$as_echo "$0: Please tell bug-autoconf@gnu.org and
273-
$0: bugs@postgrespro.ru about your system, including any
274-
$0: error possibly output before this message. Then install
275-
$0: a modern shell, or manually run the script under such a
276-
$0: shell if you do have one."
273+
$0: pgsql-bugs@postgresql.org about your system, including
274+
$0: any error possibly output before this message. Then
275+
$0: install a modern shell, or manually run the script
276+
$0: under such a shell if you do have one."
277277
fi
278278
exit 1
279279
fi
@@ -582,10 +582,10 @@ MAKEFLAGS=
582582

583583
# Identity of this package.
584584
PACKAGE_NAME='PostgreSQL'
585-
PACKAGE_TARNAME='postgrespro'
586-
PACKAGE_VERSION='9.5.2'
587-
PACKAGE_STRING='PostgreSQL 9.5.2'
588-
PACKAGE_BUGREPORT='bugs@postgrespro.ru'
585+
PACKAGE_TARNAME='postgresql'
586+
PACKAGE_VERSION='9.5.3'
587+
PACKAGE_STRING='PostgreSQL 9.5.3'
588+
PACKAGE_BUGREPORT='pgsql-bugs@postgresql.org'
589589
PACKAGE_URL=''
590590

591591
ac_unique_file="src/backend/access/common/heaptuple.c"
@@ -1400,7 +1400,7 @@ if test "$ac_init_help" = "long"; then
14001400
# Omit some internal or obsolete options to make the list less imposing.
14011401
# This message is too long to be a string in the A/UX 3.1 sh.
14021402
cat <<_ACEOF
1403-
\`configure' configures PostgreSQL 9.5.2 to adapt to many kinds of systems.
1403+
\`configure' configures PostgreSQL 9.5.3 to adapt to many kinds of systems.
14041404
14051405
Usage: $0 [OPTION]... [VAR=VALUE]...
14061406
@@ -1448,7 +1448,7 @@ Fine tuning of the installation directories:
14481448
--infodir=DIR info documentation [DATAROOTDIR/info]
14491449
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
14501450
--mandir=DIR man documentation [DATAROOTDIR/man]
1451-
--docdir=DIR documentation root [DATAROOTDIR/doc/postgrespro]
1451+
--docdir=DIR documentation root [DATAROOTDIR/doc/postgresql]
14521452
--htmldir=DIR html documentation [DOCDIR]
14531453
--dvidir=DIR dvi documentation [DOCDIR]
14541454
--pdfdir=DIR pdf documentation [DOCDIR]
@@ -1465,7 +1465,7 @@ fi
14651465

14661466
if test -n "$ac_init_help"; then
14671467
case $ac_init_help in
1468-
short | recursive ) echo "Configuration of PostgreSQL 9.5.2:";;
1468+
short | recursive ) echo "Configuration of PostgreSQL 9.5.3:";;
14691469
esac
14701470
cat <<\_ACEOF
14711471
@@ -1553,7 +1553,7 @@ Some influential environment variables:
15531553
Use these variables to override the choices made by `configure' or to help
15541554
it to find libraries and programs with nonstandard names/locations.
15551555
1556-
Report bugs to <bugs@postgrespro.ru>.
1556+
Report bugs to <pgsql-bugs@postgresql.org>.
15571557
_ACEOF
15581558
ac_status=$?
15591559
fi
@@ -1616,7 +1616,7 @@ fi
16161616
test -n "$ac_init_help" && exit $ac_status
16171617
if $ac_init_version; then
16181618
cat <<\_ACEOF
1619-
PostgreSQL configure 9.5.2
1619+
PostgreSQL configure 9.5.3
16201620
generated by GNU Autoconf 2.69
16211621
16221622
Copyright (C) 2012 Free Software Foundation, Inc.
@@ -1891,9 +1891,9 @@ $as_echo "$as_me: WARNING: $2: see the Autoconf documentation" >&2;}
18911891
$as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&2;}
18921892
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
18931893
$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
1894-
( $as_echo "## ---------------------------------- ##
1895-
## Report this to bugs@postgrespro.ru ##
1896-
## ---------------------------------- ##"
1894+
( $as_echo "## ---------------------------------------- ##
1895+
## Report this to pgsql-bugs@postgresql.org ##
1896+
## ---------------------------------------- ##"
18971897
) | sed "s/^/$as_me: WARNING: /" >&2
18981898
;;
18991899
esac
@@ -2328,7 +2328,7 @@ cat >config.log <<_ACEOF
23282328
This file contains any messages produced by compilers while
23292329
running configure, to aid debugging if configure makes a mistake.
23302330
2331-
It was created by PostgreSQL $as_me 9.5.2, which was
2331+
It was created by PostgreSQL $as_me 9.5.3, which was
23322332
generated by GNU Autoconf 2.69. Invocation command line was
23332333
23342334
$ $0 $@
@@ -18089,7 +18089,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
1808918089
# report actual input values of CONFIG_FILES etc. instead of their
1809018090
# values after options handling.
1809118091
ac_log="
18092-
This file was extended by PostgreSQL $as_me 9.5.2, which was
18092+
This file was extended by PostgreSQL $as_me 9.5.3, which was
1809318093
generated by GNU Autoconf 2.69. Invocation command line was
1809418094
1809518095
CONFIG_FILES = $CONFIG_FILES
@@ -18153,13 +18153,13 @@ $config_links
1815318153
Configuration commands:
1815418154
$config_commands
1815518155
18156-
Report bugs to <bugs@postgrespro.ru>."
18156+
Report bugs to <pgsql-bugs@postgresql.org>."
1815718157
1815818158
_ACEOF
1815918159
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
1816018160
ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
1816118161
ac_cs_version="\\
18162-
PostgreSQL config.status 9.5.2
18162+
PostgreSQL config.status 9.5.3
1816318163
configured by $0, generated by GNU Autoconf 2.69,
1816418164
with options \\"\$ac_cs_config\\"
1816518165

configure.in

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ dnl Read the Autoconf manual for details.
1717
dnl
1818
m4_pattern_forbid(^PGAC_)dnl to catch undefined macros
1919

20-
AC_INIT([PostgreSQL], [9.5.2], [bugs@postgrespro.ru],[postgrespro])
20+
AC_INIT([PostgreSQL], [9.5.3], [pgsql-bugs@postgresql.org])
2121

2222
m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.69], [], [m4_fatal([Autoconf version 2.69 is required.
2323
Untested combinations of 'autoconf' and PostgreSQL versions are not

doc/bug.template

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ System Configuration:
2323

2424
Operating System (example: Ubuntu Linux 16.04) :
2525

26-
PostgreSQL version (example: PostgresPro 9.5.1.3): PostgresPro 9.5.1.3
26+
PostgreSQL version (example: PostgresPro 9.5.3.1): PostgrePro 9.5.3.1
2727

2828
Compiler used (example: gcc 3.3.5) :
2929

doc/src/sgml/func.sgml

Lines changed: 14 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11234,13 +11234,19 @@ nextval('foo'::text) <lineannotation><literal>foo</literal> is looked up at
1123411234

1123511235
<important>
1123611236
<para>
11237-
To avoid blocking concurrent transactions that obtain numbers from the
11238-
same sequence, a <function>nextval</function> operation is never
11237+
To avoid blocking concurrent transactions that obtain numbers from
11238+
the same sequence, a <function>nextval</function> operation is never
1123911239
rolled back; that is, once a value has been fetched it is considered
11240-
used, even if the transaction that did the
11241-
<function>nextval</function> later aborts. This means that aborted
11242-
transactions might leave unused <quote>holes</quote> in the sequence
11243-
of assigned values.
11240+
used and will not be returned again. This is true even if the
11241+
surrounding transaction later aborts, or if the calling query ends
11242+
up not using the value. For example an <command>INSERT</> with
11243+
an <literal>ON CONFLICT</> clause will compute the to-be-inserted
11244+
tuple, including doing any required <function>nextval</function>
11245+
calls, before detecting any conflict that would cause it to follow
11246+
the <literal>ON CONFLICT</> rule instead. Such cases will leave
11247+
unused <quote>holes</quote> in the sequence of assigned values.
11248+
Thus, <productname>PostgreSQL</> sequence objects <emphasis>cannot
11249+
be used to obtain <quote>gapless</> sequences</emphasis>.
1124411250
</para>
1124511251
</important>
1124611252

@@ -11269,8 +11275,8 @@ nextval('foo'::text) <lineannotation><literal>foo</literal> is looked up at
1126911275
Return the value most recently returned by
1127011276
<function>nextval</> in the current session. This function is
1127111277
identical to <function>currval</function>, except that instead
11272-
of taking the sequence name as an argument it fetches the
11273-
value of the last sequence used by <function>nextval</function>
11278+
of taking the sequence name as an argument it refers to whichever
11279+
sequence <function>nextval</function> was most recently applied to
1127411280
in the current session. It is an error to call
1127511281
<function>lastval</function> if <function>nextval</function>
1127611282
has not yet been called in the current session.

doc/src/sgml/ref/create_sequence.sgml

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -239,6 +239,16 @@ SELECT * FROM <replaceable>name</replaceable>;
239239
(-9223372036854775808 to 9223372036854775807).
240240
</para>
241241

242+
<para>
243+
Because <function>nextval</> and <function>setval</> calls are never
244+
rolled back, sequence objects cannot be used if <quote>gapless</>
245+
assignment of sequence numbers is needed. It is possible to build
246+
gapless assignment by using exclusive locking of a table containing a
247+
counter; but this solution is much more expensive than sequence
248+
objects, especially if many transactions need sequence numbers
249+
concurrently.
250+
</para>
251+
242252
<para>
243253
Unexpected results might be obtained if a <replaceable
244254
class="parameter">cache</replaceable> setting greater than one is

doc/src/sgml/release-9.1.sgml

Lines changed: 165 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,171 @@
11
<!-- doc/src/sgml/release-9.1.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-9-1-22">
5+
<title>Release 9.1.22</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2016-05-12</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 9.1.21.
14+
For information about new features in the 9.1 major release, see
15+
<xref linkend="release-9-1">.
16+
</para>
17+
18+
<para>
19+
The <productname>PostgreSQL</> community will stop releasing updates
20+
for the 9.1.X release series in September 2016.
21+
Users are encouraged to update to a newer release branch soon.
22+
</para>
23+
24+
<sect2>
25+
<title>Migration to Version 9.1.22</title>
26+
27+
<para>
28+
A dump/restore is not required for those running 9.1.X.
29+
</para>
30+
31+
<para>
32+
However, if you are upgrading from a version earlier than 9.1.16,
33+
see <xref linkend="release-9-1-16">.
34+
</para>
35+
36+
</sect2>
37+
38+
<sect2>
39+
<title>Changes</title>
40+
41+
<itemizedlist>
42+
43+
<listitem>
44+
<para>
45+
Clear the OpenSSL error queue before OpenSSL calls, rather than
46+
assuming it's clear already; and make sure we leave it clear
47+
afterwards (Peter Geoghegan, Dave Vitek, Peter Eisentraut)
48+
</para>
49+
50+
<para>
51+
This change prevents problems when there are multiple connections
52+
using OpenSSL within a single process and not all the code involved
53+
follows the same rules for when to clear the error queue.
54+
Failures have been reported specifically when a client application
55+
uses SSL connections in <application>libpq</> concurrently with
56+
SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL.
57+
It's possible for similar problems to arise within the server as well,
58+
if an extension module establishes an outgoing SSL connection.
59+
</para>
60+
</listitem>
61+
62+
<listitem>
63+
<para>
64+
Fix <quote>failed to build any <replaceable>N</>-way joins</quote>
65+
planner error with a full join enclosed in the right-hand side of a
66+
left join (Tom Lane)
67+
</para>
68+
</listitem>
69+
70+
<listitem>
71+
<para>
72+
Fix possible misbehavior of <literal>TH</>, <literal>th</>,
73+
and <literal>Y,YYY</> format codes in <function>to_timestamp()</>
74+
(Tom Lane)
75+
</para>
76+
77+
<para>
78+
These could advance off the end of the input string, causing subsequent
79+
format codes to read garbage.
80+
</para>
81+
</listitem>
82+
83+
<listitem>
84+
<para>
85+
Fix dumping of rules and views in which the <replaceable>array</>
86+
argument of a <literal><replaceable>value</> <replaceable>operator</>
87+
ANY (<replaceable>array</>)</literal> construct is a sub-SELECT
88+
(Tom Lane)
89+
</para>
90+
</listitem>
91+
92+
<listitem>
93+
<para>
94+
Make <application>pg_regress</> use a startup timeout from the
95+
<envar>PGCTLTIMEOUT</> environment variable, if that's set (Tom Lane)
96+
</para>
97+
98+
<para>
99+
This is for consistency with a behavior recently added
100+
to <application>pg_ctl</>; it eases automated testing on slow machines.
101+
</para>
102+
</listitem>
103+
104+
<listitem>
105+
<para>
106+
Fix <application>pg_upgrade</> to correctly restore extension
107+
membership for operator families containing only one operator class
108+
(Tom Lane)
109+
</para>
110+
111+
<para>
112+
In such a case, the operator family was restored into the new database,
113+
but it was no longer marked as part of the extension. This had no
114+
immediate ill effects, but would cause later <application>pg_dump</>
115+
runs to emit output that would cause (harmless) errors on restore.
116+
</para>
117+
</listitem>
118+
119+
<listitem>
120+
<para>
121+
Rename internal function <function>strtoi()</>
122+
to <function>strtoint()</> to avoid conflict with a NetBSD library
123+
function (Thomas Munro)
124+
</para>
125+
</listitem>
126+
127+
<listitem>
128+
<para>
129+
Fix reporting of errors from <function>bind()</>
130+
and <function>listen()</> system calls on Windows (Tom Lane)
131+
</para>
132+
</listitem>
133+
134+
<listitem>
135+
<para>
136+
Reduce verbosity of compiler output when building with Microsoft Visual
137+
Studio (Christian Ullrich)
138+
</para>
139+
</listitem>
140+
141+
<listitem>
142+
<para>
143+
Avoid possibly-unsafe use of Windows' <function>FormatMessage()</>
144+
function (Christian Ullrich)
145+
</para>
146+
147+
<para>
148+
Use the <literal>FORMAT_MESSAGE_IGNORE_INSERTS</> flag where
149+
appropriate. No live bug is known to exist here, but it seems like a
150+
good idea to be careful.
151+
</para>
152+
</listitem>
153+
154+
<listitem>
155+
<para>
156+
Update time zone data files to <application>tzdata</> release 2016d
157+
for DST law changes in Russia and Venezuela. There are new zone
158+
names <literal>Europe/Kirov</> and <literal>Asia/Tomsk</> to reflect
159+
the fact that these regions now have different time zone histories from
160+
adjacent regions.
161+
</para>
162+
</listitem>
163+
164+
</itemizedlist>
165+
166+
</sect2>
167+
</sect1>
168+
4169
<sect1 id="release-9-1-21">
5170
<title>Release 9.1.21</title>
6171

0 commit comments

Comments
 (0)