-
Tom Lane authored
We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're using a browser or PDF reader, it's a lot nicer if it's a live hyperlink. So use "<xref>" instead. Any argument against doing this vanished with the recent decommissioning of plain-text release notes. Vik Fearing
Tom Lane authoredWe have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're using a browser or PDF reader, it's a lot nicer if it's a live hyperlink. So use "<xref>" instead. Any argument against doing this vanished with the recent decommissioning of plain-text release notes. Vik Fearing
release-8.1.sgml 154.39 KiB
<!-- doc/src/sgml/release-8.1.sgml -->
<!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-8-1-23">
<title>Release 8.1.23</title>
<note>
<title>Release Date</title>
<simpara>2010-12-16</simpara>
</note>
<para>
This release contains a variety of fixes from 8.1.22.
For information about new features in the 8.1 major release, see
<xref linkend="release-8-1">.
</para>
<para>
This is expected to be the last <productname>PostgreSQL</> release
in the 8.1.X series. Users are encouraged to update to a newer
release branch soon.
</para>
<sect2>
<title>Migration to Version 8.1.23</title>
<para>
A dump/restore is not required for those running 8.1.X.
However, if you are upgrading from a version earlier than 8.1.18,
see <xref linkend="release-8-1-18">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Force the default
<link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link>
to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp)
</para>
<para>
The default on Linux has actually been <literal>fdatasync</> for many
years, but recent kernel changes caused <productname>PostgreSQL</> to
choose <literal>open_datasync</> instead. This choice did not result
in any performance improvement, and caused outright failures on
certain filesystems, notably <literal>ext4</> with the
<literal>data=journal</> mount option.
</para>
</listitem>
<listitem>
<para>
Fix recovery from base backup when the starting checkpoint WAL record
is not in the same WAL segment as its redo point (Jeff Davis)
</para>
</listitem>
<listitem>
<para>
Add support for detecting register-stack overrun on <literal>IA64</>
(Tom Lane)
</para>
<para>