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.1beta1 Documentation"
13
HREF="index.html"><LINK
16
HREF="release.html"><LINK
18
TITLE="Release 8.1.13"
19
HREF="release-8-1-13.html"><LINK
21
TITLE="Release 8.1.11"
22
HREF="release-8-1-11.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-04-27T21:20:33"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1beta1 Documentation</A
56
TITLE="Release 8.1.13"
57
HREF="release-8-1-13.html"
74
>Appendix E. Release Notes</TD
89
TITLE="Release 8.1.11"
90
HREF="release-8-1-11.html"
104
NAME="RELEASE-8-1-12"
105
>E.65. Release 8.1.12</A
118
> This release contains a variety of fixes from 8.1.11.
119
For information about new features in the 8.1 major release, see
121
HREF="release-8-1.html"
131
>E.65.1. Migration to Version 8.1.12</A
134
> A dump/restore is not required for those running 8.1.X.
135
However, if you are upgrading from a version earlier than 8.1.2,
136
see the release notes for 8.1.2.
154
>ALTER TABLE ADD COLUMN ... PRIMARY KEY</TT
156
column is correctly checked to see if it's been initialized to all
157
non-nulls (Brendan Jurd)
160
> Previous versions neglected to check this requirement at all.
168
> failure when inheriting the
172
> constraint from multiple parent relations that
173
inherited that constraint from a common ancestor (Tom)
178
> Fix conversions between ISO-8859-5 and other encodings to handle
189
two dots) (Sergey Burladyan)
194
> Fix a few datatype input functions
195
that were allowing unused bytes in their results to contain
196
uninitialized, unpredictable values (Tom)
199
> This could lead to failures in which two apparently identical literal
200
values were not seen as equal, resulting in the parser complaining
213
> Fix a corner case in regular-expression substring matching
231
> The problem occurs when there is a match to the pattern overall but
232
the user has specified a parenthesized subexpression and that
233
subexpression hasn't got a match. An example is
236
>substring('foo' from 'foo(bar)?')</TT
238
This should return NULL, since <TT
242
it was mistakenly returning the whole-pattern match instead (ie,
251
> Update time zone data files to <SPAN
255
DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba,
256
Argentina/San_Luis, and Chile)
261
> Fix incorrect result from <SPAN
267
>PGTYPEStimestamp_sub()</CODE
273
> Fix core dump in <TT
280
> function when the input query returns a
289
>'s makefile to not override
301
> macro to not fail with <SPAN
308
> This problem affects <SPAN
311
> (V0) C functions that
312
return boolean. The fix is already in 8.3, but the need to
313
back-patch it was not realized at the time.
318
> Fix longstanding <TT
328
> In rare cases a session that had just executed a
332
> might not get a notification, even though
333
one would be expected because the concurrent transaction executing
337
> was observed to commit later.
340
> A side effect of the fix is that a transaction that has executed
341
a not-yet-committed <TT
344
> command will not see any
352
should it choose to look; formerly it would have. This behavior
353
was never documented one way or the other, but it is possible that
354
some applications depend on the old behavior.
366
prepared transaction (Tom)
369
> This was formerly allowed but trying to do it had various unpleasant
370
consequences, notably that the originating backend could not exit
374
> remained uncommitted.
379
> Fix rare crash when an error occurs during a query using a hash index
385
> Fix input of datetime values for February 29 in years BC (Tom)
388
> The former coding was mistaken about which years were leap years.
395
>"unrecognized node type"</SPAN
396
> error in some variants of
408
> to correctly extract the postmaster's port
409
number from command-line options (Itagaki Takahiro, Tom)
415
> could try to contact the
416
postmaster on the wrong port, leading to bogus reports of startup
425
> to defend against possible misoptimization
432
> This is known to be necessary when building <SPAN
444
> Fix display of constant expressions in <TT
454
> An explictly casted constant would be shown incorrectly. This could
455
for example lead to corruption of a view definition during
464
> to handle NOTICE messages correctly
465
during COPY OUT (Tom)
468
> This failure has only been observed to occur when a user-defined
469
datatype's output routine issues a NOTICE, but there is no
470
guarantee it couldn't happen due to other causes.
481
SUMMARY="Footer navigation table"
492
HREF="release-8-1-13.html"
510
HREF="release-8-1-11.html"
b'\\ No newline at end of file'