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.16"
19
HREF="release-8-1-16.html"><LINK
21
TITLE="Release 8.1.14"
22
HREF="release-8-1-14.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.16"
57
HREF="release-8-1-16.html"
74
>Appendix E. Release Notes</TD
89
TITLE="Release 8.1.14"
90
HREF="release-8-1-14.html"
104
NAME="RELEASE-8-1-15"
105
>E.62. Release 8.1.15</A
118
> This release contains a variety of fixes from 8.1.14.
119
For information about new features in the 8.1 major release, see
121
HREF="release-8-1.html"
131
>E.62.1. Migration to Version 8.1.15</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. Also, if you were running a previous
137
8.1.X release, it is recommended to <TT
141
indexes after the upgrade.
157
> Fix GiST index corruption due to marking the wrong index entry
161
> after a deletion (Teodor)
164
> This would result in index searches failing to find rows they
165
should have found. Corrupted indexes can be fixed with
174
> Fix backend crash when the client encoding cannot represent a localized
178
> We have addressed similar issues before, but it would still fail if
181
>"character has no equivalent"</SPAN
182
> message itself couldn't
183
be converted. The fix is to disable localization and send the plain
184
ASCII error message when we detect such a situation.
189
> Fix possible crash when deeply nested functions are invoked from
195
> Fix mis-expansion of rule queries when a sub-<TT
199
in a function call in <TT
212
> The usual symptom of this problem is an <SPAN
214
>"unrecognized node type"</SPAN
221
> Ensure an error is reported when a newly-defined PL/pgSQL trigger
222
function is invoked as a normal function (Tom)
227
> Prevent possible collision of <TT
231
when moving a table to another tablespace with <TT
238
> The command tried to re-use the existing filename, instead of
239
picking one that is known unused in the destination directory.
244
> Fix incorrect tsearch2 headline generation when single query
245
item matches first word of text (Sushant Sinha)
250
> Fix improper display of fractional seconds in interval values when
251
using a non-ISO datestyle in an <TT
253
>--enable-integer-datetimes</TT
267
behave correctly when the passed tuple and tuple descriptor have
268
different numbers of columns (Tom)
271
> This situation is normal when a table has had columns added or removed,
272
but these two functions didn't handle it properly.
273
The only likely consequence is an incorrect error indication.
289
> Fix recent breakage of <TT
297
> Update time zone data files to <SPAN
301
DST law changes in Argentina, Brazil, Mauritius, Syria)
312
SUMMARY="Footer navigation table"
323
HREF="release-8-1-16.html"
341
HREF="release-8-1-14.html"
b'\\ No newline at end of file'