1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.1.2 Documentation"
13
HREF="index.html"><LINK
16
HREF="release.html"><LINK
19
HREF="release-8-4.html"><LINK
21
TITLE="Release 8.3.16"
22
HREF="release-8-3-16.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-12-01T22:07:59"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1.2 Documentation</A
57
HREF="release-8-4.html"
74
>Appendix E. Release Notes</TD
80
TITLE="Release 8.3.16"
81
HREF="release-8-3-16.html"
96
>E.22. Release 8.3.17</A
109
> This release contains a variety of fixes from 8.3.16.
110
For information about new features in the 8.3 major release, see
112
HREF="release-8-3.html"
122
>E.22.1. Migration to Version 8.3.17</A
125
> A dump/restore is not required for those running 8.3.X.
128
> However, a longstanding error was discovered in the definition of the
131
>information_schema.referential_constraints</TT
133
rely on correct results from that view, you should replace its
134
definition as explained in the first changelog item below.
137
> Also, if you are upgrading from a version earlier than 8.3.8,
138
see the release notes for 8.3.8.
156
>information_schema.referential_constraints</TT
161
> This view was being insufficiently careful about matching the
162
foreign-key constraint to the depended-on primary or unique key
163
constraint. That could result in failure to show a foreign key
164
constraint at all, or showing it multiple times, or claiming that it
165
depends on a different constraint than the one it really does.
168
> Since the view definition is installed by <SPAN
172
merely upgrading will not fix the problem. If you need to fix this
173
in an existing installation, you can (as a superuser) drop the
176
>information_schema</TT
177
> schema then re-create it by sourcing
185
>/information_schema.sql</TT
189
>pg_config --sharedir</TT
190
> if you're uncertain where
196
> is.) This must be repeated in each database
202
> Fix TOAST-related data corruption during <TT
204
>CREATE TABLE dest AS
205
SELECT * FROM src</TT
208
>INSERT INTO dest SELECT * FROM src</TT
213
> If a table has been modified by <TT
215
>ALTER TABLE ADD COLUMN</TT
217
attempts to copy its data verbatim to another table could produce
218
corrupt results in certain corner cases.
219
The problem can only manifest in this precise form in 8.4 and later,
220
but we patched earlier versions as well in case there are other code
221
paths that could trigger the same bug.
226
> Fix race condition during toast table access from stale syscache entries
230
> The typical symptom was transient errors like <SPAN
233
number 0 for toast value NNNNN in pg_toast_2619"</SPAN
235
toast table would always belong to a system catalog.
242
>DatumGetInetP()</CODE
243
> unpack inet datums that have a 1-byte
244
header, and add a new macro, <CODE
246
>DatumGetInetPP()</CODE
248
not (Heikki Linnakangas)
251
> This change affects no core code, but might prevent crashes in add-on
252
code that expects <CODE
254
>DatumGetInetP()</CODE
255
> to produce an unpacked
256
datum as per usual convention.
261
> Improve locale support in <TT
264
> type's input and output
268
> Aside from not supporting all standard
270
HREF="runtime-config-client.html#GUC-LC-MONETARY"
276
formatting options, the input and output functions were inconsistent,
277
meaning there were locales in which dumped <TT
287
HREF="runtime-config-compatible.html#GUC-TRANSFORM-NULL-EQUALS"
290
>transform_null_equals</TT
295
>CASE foo WHEN NULL ...</TT
302
>transform_null_equals</TT
303
> is only supposed to affect
307
> expressions written directly by the user, not
308
equality checks generated internally by this form of <TT
316
> Change foreign-key trigger creation order to better support
317
self-referential foreign keys (Tom Lane)
320
> For a cascading foreign key that references its own table, a row update
321
will fire both the <TT
328
> trigger as one event. The <TT
332
trigger must execute first, else the <TT
336
non-final state of the row and possibly throw an inappropriate error.
337
However, the firing order of these triggers is determined by their
338
names, which generally sort in creation order since the triggers have
339
auto-generated names following the convention
342
>"RI_ConstraintTrigger_NNNN"</SPAN
343
>. A proper fix would require
344
modifying that convention, which we will do in 9.2, but it seems risky
345
to change it in existing releases. So this patch just changes the
346
creation order of the triggers. Users encountering this type of error
347
should drop and re-create the foreign key constraint to get its
348
triggers into the right order.
353
> Avoid floating-point underflow while tracking buffer allocation rate
357
> While harmless in itself, on certain platforms this would result in
358
annoying kernel log messages.
363
> Preserve blank lines within commands in <SPAN
367
history (Robert Haas)
370
> The former behavior could cause problems if an empty line was removed
371
from within a string literal, for example.
379
> to dump user-defined casts between
380
auto-generated types, such as table rowtypes (Tom Lane)
385
> Use the preferred version of <SPAN
389
not necessarily the operating system's main copy
390
(David Wheeler and Alex Hunsaker)
395
> Fix incorrect coding in <TT
397
>contrib/dict_int</TT
401
>contrib/dict_xsyn</TT
405
> Some functions incorrectly assumed that memory returned by
409
> is guaranteed zeroed.
414
> Honor query cancel interrupts promptly in <CODE
423
> Ensure VPATH builds properly install all server header files
429
> Shorten file names reported in verbose error messages (Peter Eisentraut)
432
> Regular builds have always reported just the name of the C file
433
containing the error message call, but VPATH builds formerly
434
reported an absolute path name.
439
> Fix interpretation of Windows timezone names for Central America
445
>"Central America Standard Time"</SPAN
453
>, because DST is generally not observed anywhere in
459
> Update time zone data files to <SPAN
463
for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa;
464
also historical corrections for Alaska and British East Africa.
475
SUMMARY="Footer navigation table"
486
HREF="release-8-4.html"
504
HREF="release-8-3-16.html"
b'\\ No newline at end of file'