1
1
<!-- doc/src/sgml/release-8.3.sgml -->
2
2
<!-- See header comment in release.sgml about typical markup -->
4
<sect1 id="release-8-3-17">
5
<title>Release 8.3.17</title>
8
<title>Release Date</title>
9
<simpara>2011-12-05</simpara>
13
This release contains a variety of fixes from 8.3.16.
14
For information about new features in the 8.3 major release, see
15
<xref linkend="release-8-3">.
19
<title>Migration to Version 8.3.17</title>
22
A dump/restore is not required for those running 8.3.X.
26
However, a longstanding error was discovered in the definition of the
27
<literal>information_schema.referential_constraints</> view. If you
28
rely on correct results from that view, you should replace its
29
definition as explained in the first changelog item below.
33
Also, if you are upgrading from a version earlier than 8.3.8,
34
see the release notes for 8.3.8.
40
<title>Changes</title>
46
Fix bugs in <literal>information_schema.referential_constraints</> view
51
This view was being insufficiently careful about matching the
52
foreign-key constraint to the depended-on primary or unique key
53
constraint. That could result in failure to show a foreign key
54
constraint at all, or showing it multiple times, or claiming that it
55
depends on a different constraint than the one it really does.
59
Since the view definition is installed by <application>initdb</>,
60
merely upgrading will not fix the problem. If you need to fix this
61
in an existing installation, you can (as a superuser) drop the
62
<literal>information_schema</> schema then re-create it by sourcing
63
<filename><replaceable>SHAREDIR</>/information_schema.sql</filename>.
64
(Run <literal>pg_config --sharedir</> if you're uncertain where
65
<replaceable>SHAREDIR</> is.) This must be repeated in each database
72
Fix TOAST-related data corruption during <literal>CREATE TABLE dest AS
73
SELECT * FROM src</> or <literal>INSERT INTO dest SELECT * FROM src</>
78
If a table has been modified by <command>ALTER TABLE ADD COLUMN</>,
79
attempts to copy its data verbatim to another table could produce
80
corrupt results in certain corner cases.
81
The problem can only manifest in this precise form in 8.4 and later,
82
but we patched earlier versions as well in case there are other code
83
paths that could trigger the same bug.
89
Fix race condition during toast table access from stale syscache entries
94
The typical symptom was transient errors like <quote>missing chunk
95
number 0 for toast value NNNNN in pg_toast_2619</>, where the cited
96
toast table would always belong to a system catalog.
102
Make <function>DatumGetInetP()</> unpack inet datums that have a 1-byte
103
header, and add a new macro, <function>DatumGetInetPP()</>, that does
104
not (Heikki Linnakangas)
108
This change affects no core code, but might prevent crashes in add-on
109
code that expects <function>DatumGetInetP()</> to produce an unpacked
110
datum as per usual convention.
116
Improve locale support in <type>money</> type's input and output
121
Aside from not supporting all standard
122
<link linkend="guc-lc-monetary"><varname>lc_monetary</></link>
123
formatting options, the input and output functions were inconsistent,
124
meaning there were locales in which dumped <type>money</> values could
132
linkend="guc-transform-null-equals"><varname>transform_null_equals</></link>
133
affect <literal>CASE foo WHEN NULL ...</> constructs
138
<varname>transform_null_equals</> is only supposed to affect
139
<literal>foo = NULL</> expressions written directly by the user, not
140
equality checks generated internally by this form of <literal>CASE</>.
146
Change foreign-key trigger creation order to better support
147
self-referential foreign keys (Tom Lane)
151
For a cascading foreign key that references its own table, a row update
152
will fire both the <literal>ON UPDATE</> trigger and the
153
<literal>CHECK</> trigger as one event. The <literal>ON UPDATE</>
154
trigger must execute first, else the <literal>CHECK</> will check a
155
non-final state of the row and possibly throw an inappropriate error.
156
However, the firing order of these triggers is determined by their
157
names, which generally sort in creation order since the triggers have
158
auto-generated names following the convention
159
<quote>RI_ConstraintTrigger_NNNN</>. A proper fix would require
160
modifying that convention, which we will do in 9.2, but it seems risky
161
to change it in existing releases. So this patch just changes the
162
creation order of the triggers. Users encountering this type of error
163
should drop and re-create the foreign key constraint to get its
164
triggers into the right order.
170
Avoid floating-point underflow while tracking buffer allocation rate
175
While harmless in itself, on certain platforms this would result in
176
annoying kernel log messages.
182
Preserve blank lines within commands in <application>psql</>'s command
183
history (Robert Haas)
187
The former behavior could cause problems if an empty line was removed
188
from within a string literal, for example.
194
Fix <application>pg_dump</> to dump user-defined casts between
195
auto-generated types, such as table rowtypes (Tom Lane)
201
Use the preferred version of <application>xsubpp</> to build PL/Perl,
202
not necessarily the operating system's main copy
203
(David Wheeler and Alex Hunsaker)
209
Fix incorrect coding in <filename>contrib/dict_int</> and
210
<filename>contrib/dict_xsyn</> (Tom Lane)
214
Some functions incorrectly assumed that memory returned by
215
<function>palloc()</> is guaranteed zeroed.
221
Honor query cancel interrupts promptly in <function>pgstatindex()</>
228
Ensure VPATH builds properly install all server header files
235
Shorten file names reported in verbose error messages (Peter Eisentraut)
239
Regular builds have always reported just the name of the C file
240
containing the error message call, but VPATH builds formerly
241
reported an absolute path name.
247
Fix interpretation of Windows timezone names for Central America
252
Map <quote>Central America Standard Time</> to <literal>CST6</>, not
253
<literal>CST6CDT</>, because DST is generally not observed anywhere in
260
Update time zone data files to <application>tzdata</> release 2011n
261
for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa;
262
also historical corrections for Alaska and British East Africa.
4
271
<sect1 id="release-8-3-16">
5
272
<title>Release 8.3.16</title>