Release note updates.
This commit is contained in:
Bruce Momjian
parent
a5e1cccfdb
commit
53a04e005b
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<appendix id="release">
|
<appendix id="release">
|
||||||
@ -23,11 +23,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
<variablelist>
|
<variablelist>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
Improve concurrent access to the shared buffer cache (Tom)
|
Improve concurrent access to the shared buffer cache (Tom)
|
||||||
</term>
|
</term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
This was accomplished by eliminating global locks and using a clock
|
This was accomplished by eliminating global locks and using a clock
|
||||||
sweep algorithm to find free buffers.
|
sweep algorithm to find free buffers.
|
||||||
@ -37,59 +37,87 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
Allow indexes to be used for MIN/MAX (Tom)
|
Allow indexes to be used for MIN/MAX (Tom)
|
||||||
</term>
|
</term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
In previous releases, the only way to use index for MIN/MAX was to rewrite
|
In previous releases, the only way to use index for MIN/MAX was to rewrite
|
||||||
the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens
|
the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens
|
||||||
automatically.
|
automatically.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
Add in-memory bitmaps which allows multiple indexes to be merged in a
|
Add in-memory bitmaps which allows multiple indexes to be merged in a
|
||||||
single query (Tom)
|
single query (Tom)
|
||||||
</term>
|
</term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
This allows multiple indexes to be combined to access a single
|
This allows multiple indexes to be combined to access a single
|
||||||
table.
|
table.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
</term>
|
Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
|
||||||
|
</term>
|
||||||
<listitem>
|
|
||||||
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
</para>
|
Two-phase commit allows transactions to be "prepared" on several
|
||||||
|
computers, and once all computers have successfully prepared their
|
||||||
|
transactions (and can not be rolled back) all transactions can be
|
||||||
|
committed. Even if a machine crashes after a prepare, the prepared
|
||||||
|
transaction can be committed after it is restarted. New syntax
|
||||||
|
includes PREPARE TRANSACTION and COMMIT/ROLLBACK PREPARED. A new
|
||||||
|
system view pg_prepared_xacts has also been added.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
</term>
|
Replace pg_shadow and pg_group by new role-capable catalogs pg_authid
|
||||||
|
and pg_auth_members.
|
||||||
|
</term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
</para>
|
Add SET ROLE (Stephen Frost)
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>
|
<term>
|
||||||
</term>
|
Move /contrib/pgautovacuum into the main server (Alvaro Herrera)
|
||||||
|
</term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
</para>
|
Add SET ROLE (Stephen Frost)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
|
||||||
|
<varlistentry>
|
||||||
|
<term>
|
||||||
|
Add shared row level locks using SELECT ... FOR SHARE (Alvaro)
|
||||||
|
</term>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
While PostgreSQL's MVCC locking allows SELECT to never be blocked by writers
|
||||||
|
and therefore does not need shared row locks for typical operations,
|
||||||
|
shared locks are useful for applications that require shared row locking,
|
||||||
|
and to reduce the locking requirements to maintain referential integrity.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
@ -154,6 +182,50 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Add E'' syntax so eventually normal strings can treat backslashes
|
||||||
|
literally (Bruce)
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
Currently PostgreSQL considers a backslash to be a special character
|
||||||
|
so the character after the backslash is treated specially. While this
|
||||||
|
allows easy entry of special values, it is non-standard and makes
|
||||||
|
porting of application from other databases more difficult. For this
|
||||||
|
reason, the PostgreSQL project is moving to remove the special meaning
|
||||||
|
of backslashes in strings, and allow only an E preceeding a string to
|
||||||
|
turn on the special handling of backslashes. For this reason, this
|
||||||
|
release adds several new GUC variables related to backslash
|
||||||
|
processing:
|
||||||
|
|
||||||
|
escape_string_warning - warn about backslashes in non-E strings
|
||||||
|
escape_string_syntax - does this release support the E'' syntax?
|
||||||
|
standard_conforming_strings - does this release treat backslashes
|
||||||
|
literally in non-E strings
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
The last two values are read-only and should assist in the porting of
|
||||||
|
applications. Applications can retrieve these values to know how
|
||||||
|
backslashes are processed. In a later release,
|
||||||
|
standard_conforming_strings will be true, meaning backslashes will be
|
||||||
|
treated literally in non-E strings. To prepare for this change, use
|
||||||
|
E'' strings in places that need special backslash processing, and turn
|
||||||
|
on escape_string_warning to find additional strings that need to be
|
||||||
|
converted to use E''.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Make REINDEX DATABASE reindex all indexes in the database (Tom)
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
The old behavior of REINDEX database reindexed only system tables.
|
||||||
|
This new behavior seems more intuitive. A new command REINDEX SYSTEM
|
||||||
|
allows for reindexing just the system tables.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
In psql, treat unquoted \{digit}+ sequences as octal (Bruce)
|
In psql, treat unquoted \{digit}+ sequences as octal (Bruce)
|
||||||
@ -325,6 +397,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix problem of OID wraparound conflicting with existing system objects
|
||||||
|
(Tom)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add warning about the need to increase "max_fsm_relations" and
|
Add warning about the need to increase "max_fsm_relations" and
|
||||||
@ -360,7 +439,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Allow Kerberos name and user name case sensitivity to be specified from
|
Allow Kerberos name and user name case sensitivity to be specified from
|
||||||
postgresql.conf
|
postgresql.conf (Magnus)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -401,25 +480,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Replace pg_shadow and pg_group by new role-capable catalogs pg_authid
|
|
||||||
and pg_auth_members.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Add SET ROLE (Stephen Frost)
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Move /contrib/pgautovacuum into the main server (Alvaro Herrera)
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add GUC variables to control keep-alive times for idle, interval, and
|
Add GUC variables to control keep-alive times for idle, interval, and
|
||||||
@ -433,13 +493,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Fix problem of OID wraparound conflicting with existing system objects
|
|
||||||
(Tom)
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
@ -478,18 +531,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Add shared row level locks using SELECT ... FOR SHARE (Alvaro)
|
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
While PostgreSQL's MVCC locking allows SELECT to never be blocked by writers
|
|
||||||
and therefore does not need shared row locks for typical operations,
|
|
||||||
shared locks are useful for applications that require shared row locking,
|
|
||||||
and to reduce the locking requirements to maintain referential integrity.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add BETWEEN SYMMETRIC query syntax (Pavel Stehule)
|
Add BETWEEN SYMMETRIC query syntax (Pavel Stehule)
|
||||||
@ -502,39 +543,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Add E'' syntax so eventually normal strings can treat backslashes
|
|
||||||
literally (Bruce)
|
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
Currently PostgreSQL considers a backslash to be a special character
|
|
||||||
so the character after the backslash is treated specially. While this
|
|
||||||
allows easy entry of special values, it is non-standard and makes
|
|
||||||
porting of application from other databases more difficult. For this
|
|
||||||
reason, the PostgreSQL project is moving to remove the special meaning
|
|
||||||
of backslashes in strings, and allow only an E preceeding a string to
|
|
||||||
turn on the special handling of backslashes. For this reason, this
|
|
||||||
release adds several new GUC variables related to backslash
|
|
||||||
processing:
|
|
||||||
|
|
||||||
escape_string_warning - warn about backslashes in non-E strings
|
|
||||||
escape_string_syntax - does this release support the E'' syntax?
|
|
||||||
standard_conforming_strings - does this release treat backslashes
|
|
||||||
literally in non-E strings
|
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
The last two values are read-only and should assist in the porting of
|
|
||||||
applications. Applications can retrieve these values to know how
|
|
||||||
backslashes are processed. In a later release,
|
|
||||||
standard_conforming_strings will be true, meaning backslashes will be
|
|
||||||
treated literally in non-E strings. To prepare for this change, use
|
|
||||||
E'' strings in places that need special backslash processing, and turn
|
|
||||||
on escape_string_warning to find additional strings that need to be
|
|
||||||
converted to use E''.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add NOWAIT option to SELECT ... FOR UPDATE/SHARE (Hans-Juergen Schoenig)
|
Add NOWAIT option to SELECT ... FOR UPDATE/SHARE (Hans-Juergen Schoenig)
|
||||||
@ -675,22 +683,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
|
Have initdb create new standard database called "postgres" and
|
||||||
|
convert utilities to use "postgres" rather than "template1" for
|
||||||
Two-phase commit allows transactions to be "prepared" on several
|
standard lookups (Dave)
|
||||||
computers, and once all computers have successfully prepared their
|
|
||||||
transactions (and can not be rolled back) all transactions can be
|
|
||||||
committed. Even if a machine crashes after a prepare, the prepared
|
|
||||||
transaction can be committed after it is restarted. New syntax
|
|
||||||
includes PREPARE TRANSACTION and COMMIT/ROLLBACK PREPARED. A new
|
|
||||||
system view pg_prepared_xacts has also been added.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Have initdb create new standard database called "postgres" and convert utilities
|
|
||||||
to use "postgres" rather than "template1" for standard lookups (Dave)
|
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
In prior releases, template1 was used both as a default
|
In prior releases, template1 was used both as a default
|
||||||
@ -703,17 +698,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Make REINDEX DATABASE reindex all indexes in the database (Tom)
|
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
The old behavior of REINDEX database reindexed only system tables.
|
|
||||||
This new behavior seems more intuitive. A new command REINDEX SYSTEM
|
|
||||||
allows for reindexing just the system tables.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Create new reindexdb command-line utility by moving /contrib/reindexdb
|
Create new reindexdb command-line utility by moving /contrib/reindexdb
|
||||||
@ -960,7 +944,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Change pg_stat_* views to show TOAST tables (Tom)
|
Change pg_stat_* views to show TOAST tables (Tom)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
@ -1388,7 +1374,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Streamline the passing information within the server, the optimizer,
|
Streamline the passing of information within the server, the optimizer,
|
||||||
and the lock system (Tom)
|
and the lock system (Tom)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user