Consistently indent release notes for prior releases.
This commit is contained in:
Bruce Momjian
parent
decff24fe2
commit
35dab98e1b
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.526 2007/10/18 23:05:06 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.527 2007/10/18 23:34:54 momjian Exp $ -->
|
||||
<!--
|
||||
|
||||
Typical markup:
|
||||
|
|
@ -9663,51 +9663,51 @@ data types</para></listitem>
|
|||
|
||||
<itemizedlist>
|
||||
<listitem><para>Increment the major version number of all interface
|
||||
libraries (Bruce)</para>
|
||||
libraries (Bruce)</para>
|
||||
<para>
|
||||
This should have been done in 8.0.0. It is required so 7.4.X versions
|
||||
of PostgreSQL client applications, like <application>psql</>,
|
||||
can be used on the same machine as 8.0.X applications. This might require
|
||||
re-linking user applications that use these libraries.
|
||||
This should have been done in 8.0.0. It is required so 7.4.X versions
|
||||
of PostgreSQL client applications, like <application>psql</>,
|
||||
can be used on the same machine as 8.0.X applications. This might require
|
||||
re-linking user applications that use these libraries.
|
||||
</para></listitem>
|
||||
<listitem><para>Add Windows-only <varname>wal_sync_method</> setting of
|
||||
<option>fsync_writethrough</> (Magnus, Bruce)</para>
|
||||
<option>fsync_writethrough</> (Magnus, Bruce)</para>
|
||||
<para>
|
||||
This setting causes <productname>PostgreSQL</productname> to write through
|
||||
any disk-drive write cache when writing to WAL.
|
||||
This behavior was formerly called <option>fsync</>, but was
|
||||
renamed because it acts quite differently from <option>fsync</> on other
|
||||
platforms.
|
||||
This setting causes <productname>PostgreSQL</productname> to write through
|
||||
any disk-drive write cache when writing to WAL.
|
||||
This behavior was formerly called <option>fsync</>, but was
|
||||
renamed because it acts quite differently from <option>fsync</> on other
|
||||
platforms.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>Enable the <varname>wal_sync_method</> setting of
|
||||
<option>open_datasync</> on Windows, and make it the default for that
|
||||
<option>open_datasync</> on Windows, and make it the default for that
|
||||
platform (Magnus, Bruce)</para>
|
||||
<para>
|
||||
Because the default is no longer <option>fsync_writethrough</>,
|
||||
data loss is possible during a power failure if the disk drive has
|
||||
write caching enabled. To turn off the write cache on Windows,
|
||||
from the <application>Device Manager</>, choose the drive properties,
|
||||
then <literal>Policies</>.
|
||||
Because the default is no longer <option>fsync_writethrough</>,
|
||||
data loss is possible during a power failure if the disk drive has
|
||||
write caching enabled. To turn off the write cache on Windows,
|
||||
from the <application>Device Manager</>, choose the drive properties,
|
||||
then <literal>Policies</>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>New cache management algorithm <acronym>2Q</> replaces
|
||||
<acronym>ARC</> (Tom)</para>
|
||||
<acronym>ARC</> (Tom)</para>
|
||||
<para>
|
||||
This was done to avoid a pending US patent on <acronym>ARC</>. The
|
||||
<acronym>2Q</> code might be a few percentage points slower than
|
||||
<acronym>ARC</> for some work loads. A better cache management algorithm
|
||||
will appear in 8.1.
|
||||
This was done to avoid a pending US patent on <acronym>ARC</>. The
|
||||
<acronym>2Q</> code might be a few percentage points slower than
|
||||
<acronym>ARC</> for some work loads. A better cache management algorithm
|
||||
will appear in 8.1.
|
||||
</para></listitem>
|
||||
<listitem><para>Planner adjustments to improve behavior on freshly-created
|
||||
tables (Tom)</para></listitem>
|
||||
<listitem><para>Allow plpgsql to assign to an element of an array that is
|
||||
initially <literal>NULL</> (Tom)</para>
|
||||
<para>
|
||||
Formerly the array would remain <literal>NULL</>, but now it becomes a
|
||||
single-element array. The main SQL engine was changed to handle
|
||||
<command>UPDATE</> of a null array value this way in 8.0, but the similar
|
||||
case in plpgsql was overlooked.
|
||||
Formerly the array would remain <literal>NULL</>, but now it becomes a
|
||||
single-element array. The main SQL engine was changed to handle
|
||||
<command>UPDATE</> of a null array value this way in 8.0, but the similar
|
||||
case in plpgsql was overlooked.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>Convert <literal>\r\n</> and <literal>\r</> to <literal>\n</>
|
||||
|
|
@ -9720,70 +9720,70 @@ in plpython function bodies (Michael Fuhr)</para>
|
|||
<listitem><para>Allow SPI cursors to handle utility commands that return rows,
|
||||
such as <command>EXPLAIN</> (Tom)</para></listitem>
|
||||
<listitem><para>Fix <command>CLUSTER</> failure after <command>ALTER TABLE
|
||||
SET WITHOUT OIDS</> (Tom)</para></listitem>
|
||||
SET WITHOUT OIDS</> (Tom)</para></listitem>
|
||||
<listitem><para>Reduce memory usage of <command>ALTER TABLE ADD COLUMN</>
|
||||
(Neil)</para></listitem>
|
||||
(Neil)</para></listitem>
|
||||
<listitem><para>Fix <command>ALTER LANGUAGE RENAME</> (Tom)</para></listitem>
|
||||
<listitem><para>Document the Windows-only <literal>register</> and
|
||||
<literal>unregister</> options of <application>pg_ctl</> (Magnus)</para></listitem>
|
||||
<listitem><para>Ensure operations done during backend shutdown are counted by
|
||||
statistics collector</para>
|
||||
<para>
|
||||
This is expected to resolve reports of <application>pg_autovacuum</>
|
||||
not vacuuming the system catalogs often enough — it was not being
|
||||
told about catalog deletions caused by temporary table removal during
|
||||
backend exit.
|
||||
This is expected to resolve reports of <application>pg_autovacuum</>
|
||||
not vacuuming the system catalogs often enough — it was not being
|
||||
told about catalog deletions caused by temporary table removal during
|
||||
backend exit.
|
||||
</para></listitem>
|
||||
<listitem><para>Change the Windows default for configuration parameter
|
||||
<varname>log_destination</> to <option>eventlog</> (Magnus)</para>
|
||||
<varname>log_destination</> to <option>eventlog</> (Magnus)</para>
|
||||
<para>
|
||||
By default, a server running on Windows will now send log output to the
|
||||
Windows event logger rather than standard error.
|
||||
By default, a server running on Windows will now send log output to the
|
||||
Windows event logger rather than standard error.
|
||||
</para></listitem>
|
||||
<listitem><para>Make Kerberos authentication work on Windows (Magnus)</para></listitem>
|
||||
<listitem><para>Allow <command>ALTER DATABASE RENAME</> by superusers
|
||||
who aren't flagged as having CREATEDB privilege (Tom)</para></listitem>
|
||||
who aren't flagged as having CREATEDB privilege (Tom)</para></listitem>
|
||||
<listitem><para>Modify WAL log entries for <command>CREATE</> and
|
||||
<command>DROP DATABASE</> to not specify absolute paths (Tom)</para>
|
||||
<para>This allows point-in-time recovery on a different machine with possibly
|
||||
different database location. Note that <command>CREATE TABLESPACE</> still
|
||||
poses a hazard in such situations.
|
||||
<para>This allows point-in-time recovery on a different machine with possibly
|
||||
different database location. Note that <command>CREATE TABLESPACE</> still
|
||||
poses a hazard in such situations.
|
||||
</para></listitem>
|
||||
<listitem><para>Fix crash from a backend exiting with an open transaction
|
||||
that created a table and opened a cursor on it (Tom)</para></listitem>
|
||||
that created a table and opened a cursor on it (Tom)</para></listitem>
|
||||
<listitem><para>Fix <function>array_map()</> so it can call PL functions
|
||||
(Tom)</para></listitem>
|
||||
(Tom)</para></listitem>
|
||||
<listitem><para>Several <filename>contrib/tsearch2</> and
|
||||
<filename>contrib/btree_gist</> fixes (Teodor)
|
||||
</para></listitem>
|
||||
</para></listitem>
|
||||
<listitem><para>Fix crash of some <filename>contrib/pgcrypto</>
|
||||
functions on some platforms (Marko Kreen)</para></listitem>
|
||||
functions on some platforms (Marko Kreen)</para></listitem>
|
||||
<listitem><para>Fix <filename>contrib/intagg</> for 64-bit platforms
|
||||
(Tom)</para></listitem>
|
||||
(Tom)</para></listitem>
|
||||
<listitem><para>Fix ecpg bugs in parsing of <command>CREATE</> statement
|
||||
(Michael)</para></listitem>
|
||||
(Michael)</para></listitem>
|
||||
<listitem><para>Work around gcc bug on powerpc and amd64 causing problems in
|
||||
ecpg (Christof Petig)</para></listitem>
|
||||
ecpg (Christof Petig)</para></listitem>
|
||||
<listitem><para>Do not use locale-aware versions of <function>upper()</>,
|
||||
<function>lower()</>, and <function>initcap()</> when the locale is
|
||||
<literal>C</> (Bruce)</para>
|
||||
<function>lower()</>, and <function>initcap()</> when the locale is
|
||||
<literal>C</> (Bruce)</para>
|
||||
<para>
|
||||
This allows these functions to work on platforms that generate errors
|
||||
for non-7-bit data when the locale is <literal>C</>.
|
||||
</para></listitem>
|
||||
<listitem><para>Fix <function>quote_ident()</> to quote names that match keywords (Tom)</para></listitem>
|
||||
<listitem><para>Fix <function>to_date()</> to behave reasonably when
|
||||
<literal>CC</> and <literal>YY</> fields are both used (Karel)</para></listitem>
|
||||
<literal>CC</> and <literal>YY</> fields are both used (Karel)</para></listitem>
|
||||
<listitem><para>Prevent <function>to_char(interval)</> from failing
|
||||
when given a zero-month interval (Tom)</para></listitem>
|
||||
when given a zero-month interval (Tom)</para></listitem>
|
||||
<listitem><para>Fix wrong week returned by <function>date_trunc('week')</>
|
||||
(Bruce)</para>
|
||||
<para>
|
||||
<function>date_trunc('week')</>
|
||||
returned the wrong year for the first few days of January in some years.
|
||||
<function>date_trunc('week')</>
|
||||
returned the wrong year for the first few days of January in some years.
|
||||
</para></listitem>
|
||||
<listitem><para>Use the correct default mask length for class <literal>D</>
|
||||
addresses in <type>INET</> data types (Tom)</para></listitem>
|
||||
addresses in <type>INET</> data types (Tom)</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
|
|
@ -13040,10 +13040,10 @@ This error only occurred when the
|
|||
<listitem><para>Ensure operations done during backend shutdown are counted by
|
||||
statistics collector</para>
|
||||
<para>
|
||||
This is expected to resolve reports of <application>pg_autovacuum</>
|
||||
not vacuuming the system catalogs often enough — it was not being
|
||||
told about catalog deletions caused by temporary table removal during
|
||||
backend exit.
|
||||
This is expected to resolve reports of <application>pg_autovacuum</>
|
||||
not vacuuming the system catalogs often enough — it was not being
|
||||
told about catalog deletions caused by temporary table removal during
|
||||
backend exit.
|
||||
</para></listitem>
|
||||
<listitem><para>Additional buffer overrun checks in plpgsql
|
||||
(Neil)</para></listitem>
|
||||
|
|
@ -13597,9 +13597,9 @@ DROP SCHEMA information_schema CASCADE;
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-4">
|
||||
<sect1 id="release-7-4">
|
||||
<title>Release 7.4</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -15457,7 +15457,7 @@ DROP SCHEMA information_schema CASCADE;
|
|||
</itemizedlist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-20">
|
||||
<title>Release 7.3.20</title>
|
||||
|
|
@ -16169,7 +16169,7 @@ month-related formats</para></listitem>
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-9">
|
||||
<title>Release 7.3.9</title>
|
||||
|
|
@ -16225,7 +16225,7 @@ datestyles</para></listitem>
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-8">
|
||||
<title>Release 7.3.8</title>
|
||||
|
|
@ -16275,7 +16275,7 @@ concern since there is no reason for non-developers to use this script anyway.
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-7">
|
||||
<title>Release 7.3.7</title>
|
||||
|
|
@ -16315,7 +16315,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-6">
|
||||
<title>Release 7.3.6</title>
|
||||
|
|
@ -16380,7 +16380,7 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-5">
|
||||
<title>Release 7.3.5</title>
|
||||
|
|
@ -16431,7 +16431,7 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-4">
|
||||
<title>Release 7.3.4</title>
|
||||
|
|
@ -16473,7 +16473,7 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-3-3">
|
||||
<sect1 id="release-7-3-3">
|
||||
<title>Release 7.3.3</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -16580,10 +16580,10 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
<listitem><para>Better error message for character set conversion problems in JDBC</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-3-2">
|
||||
<sect1 id="release-7-3-2">
|
||||
<title>Release 7.3.2</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -16641,10 +16641,10 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
<listitem><para>fastpath code now checks for privilege to call function</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-3-1">
|
||||
<sect1 id="release-7-3-1">
|
||||
<title>Release 7.3.1</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -16691,10 +16691,10 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
<listitem><para>Prevent composite column creation via ALTER TABLE (Tom)</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-3">
|
||||
<sect1 id="release-7-3">
|
||||
<title>Release 7.3</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -17328,7 +17328,7 @@ operations on bytea columns (Joe)</para></listitem>
|
|||
</sect3>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-2-8">
|
||||
<title>Release 7.2.8</title>
|
||||
|
|
@ -17379,7 +17379,7 @@ month-related formats</para></listitem>
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-2-7">
|
||||
<title>Release 7.2.7</title>
|
||||
|
|
@ -17427,7 +17427,7 @@ datestyles</para></listitem>
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-2-6">
|
||||
<title>Release 7.2.6</title>
|
||||
|
|
@ -17478,7 +17478,7 @@ concern since there is no reason for non-developers to use this script anyway.
|
|||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-2-5">
|
||||
<title>Release 7.2.5</title>
|
||||
|
|
@ -17521,9 +17521,9 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
<listitem><para>Avoid conflict with system definition of <function>isblank()</function> function or macro</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-2-4">
|
||||
<sect1 id="release-7-2-4">
|
||||
<title>Release 7.2.4</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -17559,10 +17559,10 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
<listitem><para>Repair long-standing logic errors in lseg_eq(), lseg_ne(), lseg_center()</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-2-3">
|
||||
<sect1 id="release-7-2-3">
|
||||
<title>Release 7.2.3</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -17596,10 +17596,10 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
<listitem><para>Fix <application>pg_dump</> to properly dump FULL JOIN USING (Tom)</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-2-2">
|
||||
<sect1 id="release-7-2-2">
|
||||
<title>Release 7.2.2</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -17639,10 +17639,10 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
<listitem><para>Fix for repeat(), lpad(), rpad() and long strings (Neil)</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-2-1">
|
||||
<sect1 id="release-7-2-1">
|
||||
<title>Release 7.2.1</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -17685,10 +17685,10 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
<listitem><para>Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-2">
|
||||
<sect1 id="release-7-2">
|
||||
<title>Release 7.2</title>
|
||||
|
||||
<note>
|
||||
|
|
@ -18241,7 +18241,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
|||
</itemizedlist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="release-7-1-3">
|
||||
|
|
|
|||
Loading…
Reference in New Issue