Skip to content

P
Postgres FD Implementation
Commit bc1a3cdd authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Update release notes.

parent 31ef0588
Show whitespace changes
Inline Side-by-side
Showing with 623 additions and 426 deletions
doc/src/sgml/release.sgml
View file @ bc1a3cdd
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.346 2005/08/23 19:44:58 momjian Exp $
--> -->
<appendix id="release"> <appendix id="release">
...@@ -29,23 +29,25 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -29,23 +29,25 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<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
sweep algorithm to find free buffers. This increases scalability clock sweep algorithm to find free buffers. This increases
on multi-CPU systems. scalability on multi-CPU systems.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
Automatically use indexes for MIN() and MAX() (Tom) Automatically use indexes for <function>MIN()</> and
<function>MAX()</> (Tom)
</term> </term>
<listitem> <listitem>
<para> <para>
In previous releases, the only way to use an index for MIN/MAX In previous releases, the only way to use an index for
was to rewrite the query as SELECT col FROM tab ORDER BY col <function>MIN()</> or <function>MAX()</> was to rewrite the
LIMIT 1. Index usage now happens automatically. query as <command>SELECT col FROM tab ORDER BY col LIMIT 1</>.
Index usage now happens automatically.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -59,15 +61,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -59,15 +61,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
In previous releases, only a single index could be used to do In previous releases, only a single index could be used to do
lookups on a table. With this feature, if a query has WHERE lookups on a table. With this feature, if a query has
tab.col1 = 4 and tab.col2 = 9, and there is no multicolumn index <command>WHERE tab.col1 = 4 and tab.col2 = 9</>, and there is no
on col1 and col2, but there is an index on col1 and another on multicolumn index on col1 and col2, but there is an index on
col2, it is possible to do lookups on the col1 index and the col1 and another on col2, it is possible to do lookups on the
col2 index and combine them in memory to do heap lookups on rows col1 index and the col2 index and combine them in memory to do
matching both the col1 and col2 restrictions. This is very heap lookups on rows matching both the col1 and col2
useful in environments that have a lot of unstructured queries restrictions. This is very useful in environments that have a
where it is impossible to create indexes that match all possible lot of unstructured queries where it is impossible to create
access conditions. indexes that match all possible access conditions.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -84,9 +86,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -84,9 +86,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
their transactions (none failed), all transactions can be their transactions (none failed), all transactions can be
committed. Even if a machine crashes after a prepare, the committed. Even if a machine crashes after a prepare, the
prepared transaction can be committed after it is restarted. New prepared transaction can be committed after it is restarted. New
syntax includes PREPARE TRANSACTION and COMMIT/ROLLBACK syntax includes <command>PREPARE TRANSACTION</> and
PREPARED. A new system view pg_prepared_xacts has also been <command>COMMIT/ROLLBACK PREPARED</>. A new system view
added. pg_prepared_xacts has also been added.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -127,48 +129,52 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -127,48 +129,52 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Switch to another member role using SET ROLE Switch to another member role using <command>SET ROLE</>
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para> <para>
So, once a user logs into a role, she inherits capabilities of So, once a user logs into a role, she inherits capabilities of
the login role plus any inherited roles, and can use SET ROLE to the login role plus any inherited roles, and can use
switch to other member roles. This change also replaces <command>SET ROLE</> to switch to other member roles. This
pg_shadow and pg_group by with new role-capable catalogs change also replaces pg_shadow and pg_group by with new
pg_authid and pg_auth_members. The old tables are redefined as role-capable catalogs pg_authid and pg_auth_members. The old
views on the new role tables. tables are redefined as views on the new role tables.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
Move /contrib/pgautovacuum into the main server (Alvaro Herrera) Move <filename>/contrib/pgautovacuum</> into the main server
(Alvaro Herrera)
</term> </term>
<listitem> <listitem>
<para> <para>
Moving pgautovacuum from /contrib allows it to be automatically Moving pgautovacuum from <filename>/contrib</> allows it to be
started and stoped in sync with the database server, and allows automatically started and stoped in sync with the database
for pgautovacuum to be configured from postgresql.conf. server, and allows for pgautovacuum to be configured from
postgresql.conf.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
Add shared row level locks using SELECT ... FOR SHARE (Alvaro) Add shared row level locks using <command>SELECT ... FOR SHARE</>
(Alvaro)
</term> </term>
<listitem> <listitem>
<para> <para>
While PostgreSQL's MVCC locking allows SELECT to never be While <productname>PostgreSQL</productname>'s MVCC locking
blocked by writers and therefore does not need shared row locks allows <command>SELECT</> to never be blocked by writers and
for typical operations, shared locks are useful for applications therefore does not need shared row locks for typical operations,
that require shared row locking, and to reduce the locking shared locks are useful for applications that require shared row
requirements to maintain referential integrity. locking, and to reduce the locking requirements to maintain
referential integrity.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -180,16 +186,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -180,16 +186,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<title>Migration to version 8.1</title> <title>Migration to version 8.1</title>
<para> <para>
A dump/restore using <application>pg_dump</application> is A dump/restore using <application>pg_dump</application> is required
required for those wishing to migrate data from any previous for those wishing to migrate data from any previous release.
release.
</para> </para>
<para> <para>
The 8.0 release announced that the <function>to_char()</> function The 8.0 release announced that the <function>to_char()</> function
for intervals would be removed in 8.1. However, since no better API has been for intervals would be removed in 8.1. However, since no better API
suggested, to_char(interval) has been enhanced in 8.1 and will remain in the has been suggested, to_char(interval) has been enhanced in 8.1 and
server. will remain in the server.
</para> </para>
<para> <para>
...@@ -203,131 +208,142 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -203,131 +208,142 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Change add_missing_from to 'false' Change add_missing_from to 'false'
</para> </para>
<para> <para>
Generate an error if a table used in a query without a FROM reference (Neil) Generate an error if a table used in a query without a
No more SELECT pg_class.*; <command>FROM</> reference (Neil) This command, <command>SELECT
pg_class.*</>, now generates an error.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Cause input of a zero-length strings ('') for float4/float8/oid to throw Cause input of a zero-length strings ('') for float4/float8/oid
an error, rather than treat it as a zero (Neil) to throw an error, rather than treat it as a zero (Neil)
</para> </para>
<para> <para>
This change is consistent with the current handling of zero-length This change is consistent with the current handling of
strings for integers. The schedule for this change was announced in 8.0. zero-length strings for integers. The schedule for this change
was announced in 8.0.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Change the default for default_with_oids to false (Neil) Change <varname>default_with_oids</> to default to false (Neil)
</para> </para>
<para> <para>
With this option set to false, user-created tables no With this option set to false, user-created tables no longer have
longer have an the usually-invisible OID column unless WITH OIDS an the usually-invisible OID column unless <command>WITH OIDS</>
is specified in CREATE TABLE. Though OIDs have existed in all previous is specified in <command>CREATE TABLE</>. Though OIDs have
releases of PostgreSQL, their use is limited because they are only four existed in all previous releases of
bytes long and the counter is unique across all installed databases. <productname>PostgreSQL</productname>, their use is limited
The preferred way of uniquely identifying rows is via sequences and because they are only four bytes long and the counter is unique
SERIAL, which has been supported since PostgreSQL 6.4. across all installed databases. The preferred way of uniquely
identifying rows is via sequences and <command>SERIAL</>, which
has been supported since <productname>PostgreSQL</productname>
6.4.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add E'' syntax so eventually ordinary strings can treat backslashes Add <literal>E''</> syntax so eventually ordinary strings can
literally (Bruce) treat backslashes literally (Bruce)
</para> </para>
<para> <para>
Currently PostgreSQL processes a backslash in a string Currently <productname>PostgreSQL</productname> processes a
as preceeding a character that requires special processing, e.g. backslash in a string as preceeding a character that requires
\n or \010. While this allows easy entry of special values, it is special processing, e.g. <literal>\n</> or <literal>\010</>.
While this allows easy entry of special values, it is
non-standard and makes porting of application from other non-standard and makes porting of application from other
databases more difficult. For this reason, the PostgreSQL project databases more difficult. For this reason, the
is planning to remove the special meaning of backslashes in <productname>PostgreSQL</productname> project is planning to
strings. For backward compatibility and for users who want remove the special meaning of backslashes in strings. For
special backslash procesing, a new string type will be created. backward compatibility and for users who want special backslash
This new string type is formed by having an E preceed procesing, a new string type will be created. This new string
the single quote that starts the string, e.g. E'hi\n'. type is formed by having an E preceed the single quote that
While this release does not change the handling of backslashes in starts the string, e.g. <literal>E'hi\n'</>. While this release
strings, it does add several new GUC variables to help users does not change the handling of backslashes in strings, it does
migrate applications for future releases: add several new GUC variables to help users migrate applications
for future releases:
</para> </para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
escape_string_warning - warn about backslashes in ordinary <varname>escape_string_warning</> - warn about backslashes in
(non-E) strings ordinary (non-E) strings
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
escape_string_syntax - does this release support the E'' syntax? <varname>escape_string_syntax</> - does this release support
the E'' syntax?
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
standard_conforming_strings - does this release treat <varname>standard_conforming_strings>/> - does this release
backslashes literally in normal strings? treat backslashes literally in normal strings?
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para> <para>
The last two values are read-only and should assist in the porting of The last two values are read-only and should assist in the
applications. Applications can retrieve these values to know how porting of applications. Applications can retrieve these values
backslashes are processed. In a later release, to know how backslashes are processed. In a later release,
standard_conforming_strings will be true, meaning backslashes will be standard_conforming_strings will be true, meaning backslashes
treated literally in non-E strings. To prepare for this change, use will be treated literally in non-E strings. To prepare for this
E'' strings in places that need special backslash processing, and turn change, use E'' strings in places that need special backslash
on escape_string_warning to find additional strings that need to be processing, and turn on escape_string_warning to find additional
converted to use E''. strings that need to be converted to use <literal>E''</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Make REINDEX DATABASE reindex all indexes in the database (Tom) Make <command>REINDEX DATABASE</> reindex all indexes in the
database (Tom)
</para> </para>
<para> <para>
The old behavior of REINDEX database reindexed only system tables. The old behavior of <command>REINDEX</> database reindexed only
This new behavior seems more intuitive. A new command REINDEX SYSTEM system tables. This new behavior seems more intuitive. A new
allows for reindexing just the system tables. command <command>REINDEX SYSTEM</> allows for reindexing just the
system tables.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
In psql, treat unquoted \{digit}+ sequences as octal (Bruce) In psql, treat unquoted <literal>\{digit}+</> sequences as octal
(Bruce)
</para> </para>
<para> <para>
In previous releases, \{digit}+ sequences were treated as In previous releases, <literal>\{digit}+</> sequences were
decimal, and only \0{digit}+ were treated as octal. This treated as decimal, and only <literal>\0{digit}+</> were treated
change was made for consistency. as octal. This change was made for consistency.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Remove grammar productions for prefix and postfix % and ^ operators Remove grammar productions for prefix and postfix <literal>%</>
and <literal>^</> operators
(Tom) (Tom)
</para> </para>
<para> <para>
These have never been documented and complicated the use of the modulus These have never been documented and complicated the use of the
operator (%) with negative numbers. modulus operator (<literal>%</>) with negative numbers.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Make "&amp;&lt;" and "&amp;&gt;" for polygons consistent with the box Make <literal>&amp;&lt;</> and <literal>&amp;&gt;</> for polygons
"over" operators (Tom) consistent with the box "over" operators (Tom)
</para> </para>
</listitem> </listitem>
...@@ -354,7 +370,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -354,7 +370,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Improve the optimizer, including auto-resizing of hash joins (Tom) Improve the optimizer, including auto-resizing of hash joins
(Tom)
</para> </para>
</listitem> </listitem>
...@@ -378,22 +395,25 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -378,22 +395,25 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Allow non-consecutive index columns to be used in a multi-column index Allow non-consecutive index columns to be used in a multi-column
index
(Tom) (Tom)
</para> </para>
<para> <para>
For example, this allows an index on columns a,b,c to be used in a For example, this allows an index on columns a,b,c to be used in
query with WHERE a = 4 and c = 10 a query with <command>WHERE a = 4 and c = 10</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Skip WAL logging for CREATE TABLE AS / SELECT INTO (Simon) Skip WAL logging for <command>CREATE TABLE AS</> /
<command>SELECT INTO</> (Simon)
</para> </para>
<para> <para>
Since a crash during CREATE TABLE would cause the table to be dropped Since a crash during <command>CREATE TABLE</> would cause the
during recovery, there is no reason to WAL log as the table is loaded. table to be dropped during recovery, there is no reason to WAL
log as the table is loaded.
</para> </para>
</listitem> </listitem>
...@@ -405,48 +425,52 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -405,48 +425,52 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add GUC full_page_writes to control writing full pages to WAL (Bruce) Add GUC <varname>full_page_writes</> to control writing full
pages to WAL
(Bruce)
</para> </para>
<para> <para>
To prevent partial disk writes from corrupting the database, To prevent partial disk writes from corrupting the database,
PostgreSQL writes a complete copy of each database disk page to WAL <productname>PostgreSQL</productname> writes a complete copy of
the first time it is modified after a checkpoint. This turns off that each database disk page to WAL the first time it is modified
functionality for users with battery-backed disk caches where partial after a checkpoint. This turns off that functionality for users
page writes cannot happen. with battery-backed disk caches where partial page writes cannot
happen.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add constraint_exclusion to restrict child table lookups based on Add constraint_exclusion to restrict child table lookups based
table constraints (Simon) on table constraints (Simon)
</para> </para>
<para> <para>
This allows for a type of table partitioning. If child table placed This allows for a type of table partitioning. If child table
in a different tablespaces using appropriate CHECK constraints, the placed in a different tablespaces using appropriate
optimizer will skip child table accesses if the constraint guarantees <command>CHECK</> constraints, the optimizer will skip child
no matching rows exist in the child table. table accesses if the constraint guarantees no matching rows
exist in the child table.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Use O_DIRECT if available when using O_SYNC for wal_sync_method (ITAGAKI Use <literal>O_DIRECT</> if available when using
Takahiro) <literal>O_SYNC</> for wal_sync_method (Itagaki Takahiro)
</para> </para>
<para> <para>
O_DIRECT causes disk writes to bypass the kernel cache, and for WAL <literal>O_DIRECT</> causes disk writes to bypass the kernel
writes, this improves performance. cache, and for WAL writes, this improves performance.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Improve COPY FROM performance (Alon Goldshuv) Improve <command>COPY FROM</> performance (Alon Goldshuv)
</para> </para>
<para> <para>
This was accomplished by reading COPY input in larger chunks, rather This was accomplished by reading <command>COPY</> input in
than character by character. larger chunks, rather than character by character.
</para> </para>
</listitem> </listitem>
...@@ -463,74 +487,80 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -463,74 +487,80 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Prevent problems due to transaction ID (XID) wraparound (Tom) Prevent problems due to transaction ID (XID) wraparound (Tom)
</para> </para>
<para> <para>
This was accomplished by warning the transaction counter is This was accomplished by warning the transaction counter is near
near the the earliest transaction id determined by the the the earliest transaction id determined by the database whose
database whose last vacuum is the oldest. If the limit is last vacuum is the oldest. If the limit is reached, the server
reached, the server will no longer accept queries. will no longer accept queries.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Fix problem of object ID (OID) wraparound conflicting Fix problem of object ID (OID) wraparound conflicting with
with existing system objects (Tom) existing system objects (Tom)
</para> </para>
</listitem> </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_pages" during VACUUM (Ron Mayer) <varname>max_fsm_relations</> and <varname>max_fsm_pages</>
during <command>VACUUM</> (Ron Mayer)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add temp_buffers GUC variable to allow users to determine the size Add <varname>temp_buffers</> GUC variable to allow users to
of the local buffer area for temporary table access (Tom) determine the size of the local buffer area for temporary table
access (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add session start time and client IP address to pg_stat_activity (Magnus) Add session start time and client IP address to
<literal>pg_stat_activity</> (Magnus)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Enhance pg_locks display (Tom) Enhance <literal>pg_locks</> display (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Log queries for client-side PREPARE and EXECUTE (Simon) Log queries for client-side <command>PREPARE</> and
<command>EXECUTE</> (Simon)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow Kerberos name and user name case sensitivity to be Allow Kerberos name and user name case sensitivity to be
specified in postgresql.conf (Magnus) specified in <filename>postgresql.conf</> (Magnus)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add GUC krb_server_hostname so the server hostname can be specified as Add GUC <varname>krb_server_hostname</> so the server hostname
part of service principal (Todd Kover) can be specified as part of service principal (Todd Kover)
</para> </para>
<para> <para>
If not set, any service principal matching an entry in the keytab If not set, any service principal matching an entry in the
can be used. This is new Kerberos matching behavior in this release. keytab can be used. This is new Kerberos matching behavior in
this release.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add log_line_prefix options for millisecond timestamps (%m) and Add <varname>log_line_prefix</> options for millisecond
remote host (%h) (Ed L.) timestamps (<literal>%m</>) and remote host (<literal>%h</>) (Ed
L.)
</para> </para>
</listitem> </listitem>
...@@ -539,17 +569,18 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -539,17 +569,18 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Add WAL logging for GIST indexes (Teodor, Oleg) Add WAL logging for GIST indexes (Teodor, Oleg)
</para> </para>
<para> <para>
GIST indexes now work for point-in-time recovery and crash recovery GIST indexes are now safe for crash and point-in-time recovery
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Remove old *.backup files when we do pg_stop_backup() (Bruce) Remove old <filename>*.backup</> files when we do
<function>pg_stop_backup()</> (Bruce)
</para> </para>
<para> <para>
This prevents a large number of *.backup files from existing in This prevents a large number of <filename>*.backup</> files from
/seemspg_xlog. existing in <filename>/pg_xlog</>.
</para> </para>
</listitem> </listitem>
...@@ -565,10 +596,10 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -565,10 +596,10 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Add per-user and per-database connection limits (Petr Jelinek) Add per-user and per-database connection limits (Petr Jelinek)
</para> </para>
<para> <para>
Using ALTER USER and ALTER DATABASE, limits can not be enforced Using <command>ALTER USER</> and <command>ALTER DATABASE</>,
on the maximum number of users who can connect as as a specific limits can not be enforced on the maximum number of users who
uesr or to a specific database. Setting the limit to zero can connect as as a specific uesr or to a specific database.
disables user or database connections. Setting the limit to zero disables user or database connections.
</para> </para>
</listitem> </listitem>
...@@ -588,57 +619,63 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -588,57 +619,63 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Fix HAVING without aggregate functions and no GROUP BY to behave Fix <command>HAVING</> without aggregate functions and no
as if the main query returns a single group (Tom) <command>GROUP BY</> to behave as if the main query returns a
single group (Tom)
</para> </para>
<para> <para>
Previously, such a case would treat the HAVING clause as WHERE Previously, such a case would treat the <command>HAVING</>
clause. clause as <command>WHERE</> clause.
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add USING clause to allow additional tables to be specified to DELETE Add <command>USING</> clause to allow additional tables to be
(Euler Taveira de Oliveira) specified to <command>DELETE</> (Euler Taveira de Oliveira)
</para> </para>
<para> <para>
In prior releases, there was no clear method for specifying In prior releases, there was no clear method for specifying
additional tables to be used for joins in a DELETE statement. additional tables to be used for joins in a <command>DELETE</>
UPDATE already has a FROM clause for this purpose. statement. <command>UPDATE</> already has a <command>FROM</>
clause for this purpose.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for \x hex escapes in backend and ecpg strings (Bruce) Add support for <literal>\x</> hex escapes in backend and ecpg
strings (Bruce)
</para> </para>
<para> <para>
This is just like the standar C \x escape syntax. Octal was already This is just like the standard C <literal>\x</> escape syntax.
supported. Octal escapes were already supported.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add BETWEEN SYMMETRIC query syntax (Pavel Stehule) Add <command>BETWEEN SYMMETRIC</> query syntax (Pavel Stehule)
</para> </para>
<para> <para>
This feature allows BETWEEN comparisons without requiring the This feature allows <command>BETWEEN</> comparisons without
first value to be less than the second. For example, 2 BETWEEN requiring the first value to be less than the second. For
[ASYMMETRIC] 3 AND 1 returns false, while 2 BETWEEN SYMMETRIC 3 example, <command>2 BETWEEN [ASYMMETRIC] 3 AND 1</> returns
AND 1 returns true. BETWEEN ASYMMETRIC was already supported. false, while <command>2 BETWEEN SYMMETRIC 3 AND 1</> returns
true. <command>BETWEEN ASYMMETRIC</> was already supported.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add NOWAIT option to SELECT ... FOR UPDATE/SHARE (Hans-Juergen Schoenig) Add <command>NOWAIT</> option to <command>SELECT ... FOR
UPDATE/SHARE</> (Hans-Juergen Schoenig)
</para> </para>
<para> <para>
While SET statement_timeout allows a query taking over a certain While <command>SET</> statement_timeout allows a query taking
amount of time to be cancelled, the NO WAIT option allows a query to over a certain amount of time to be cancelled, the <command>NO
be canceled as soon as a SELECT ... FOR UPDATE/SHARE cannot WAIT</> option allows a query to be canceled as soon as a
immediately acquire a row lock. <command>SELECT ... FOR UPDATE/SHARE</> cannot immediately
acquire a row lock.
</para> </para>
</listitem> </listitem>
...@@ -655,31 +692,32 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -655,31 +692,32 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Track dependencies of shared objects (Alvaro) Track dependencies of shared objects (Alvaro)
</para> </para>
<para> <para>
PostgreSQL allows global tables (users, databases, tablespaces) to <productname>PostgreSQL</productname> allows global tables
reference information in multiple databases. This addition adds (users, databases, tablespaces) to reference information in
dependency information for global tables, so, for example, user multiple databases. This addition adds dependency information
ownership can be tracked across databases, so a user who owns for global tables, so, for example, user ownership can be
something in any database can no longer be removed. Dependency tracked across databases, so a user who owns something in any
tracking already existed for database-local objects. database can no longer be removed. Dependency tracking already
existed for database-local objects.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow ALTER OWNER commands to be performed by the object owner as Allow <command>ALTER OWNER</> commands to be performed by the
well as the superuser (Stephen Frost) object owner as well as the superuser (Stephen Frost)
</para> </para>
<para> <para>
Prior releases only allowed super-user to change object owners, even Prior releases only allowed super-user to change object owners,
if the current owner was executing the command and the new owner even if the current owner was executing the command and the new
have permission to create objects of that type. owner have permission to create objects of that type.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add ALTER object SET SCHEMA capability for some object types Add <command>ALTER</> object <command>SET SCHEMA</> capability
(tables, functions, types) (Bernd Helmle) for some object types (tables, functions, types) (Bernd Helmle)
</para> </para>
<para> <para>
This allows objects to be moved to different schemas. This allows objects to be moved to different schemas.
...@@ -696,62 +734,66 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -696,62 +734,66 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Allow TRUNCATE to truncate multiple files in a single command (Alvaro) Allow <command>TRUNCATE</> to truncate multiple files in a
single command (Alvaro)
</para> </para>
<para> <para>
Because of referential integrity checks, it is impossible to truncate Because of referential integrity checks, it is impossible to
a table that is part of a referential integrity constraint. Using this truncate a table that is part of a referential integrity
new functionality, TRUNCATE can be used to truncate all tables constraint. Using this new functionality, <command>TRUNCATE</>
involved in referential integrity if they are truncated in a can be used to truncate all tables involved in referential
single TRUNCATE command. integrity if they are truncated in a single <command>TRUNCATE</>
command.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Properly process carriage returns and line feeds in COPY CSV mode Properly process carriage returns and line feeds in
(Andrew Dunstan) <command>COPY CSV</> mode (Andrew Dunstan)
</para> </para>
<para> <para>
In release 8.0, carriage returns and line feeds in CSV COPY TO were In release 8.0, carriage returns and line feeds in <command>CSV
processed in an inconsistent manner. (This was documented on the TODO COPY TO</> were processed in an inconsistent manner. (This was
list.) documented on the TODO list.)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <command>COPY WITH CSV HEADER</> to allow a header line as
Add COPY WITH CSV HEADER to allow a heading line as the first line in the first line in <command>COPY</> (Andrew)
COPY (Andrew)
</para> </para>
<para> <para>
This allows handling of the common CSV usage of placing the column This allows handling of the common <command>CSV</> usage of
names on the first line of the data file. For COPY TO, the first line placing the column names on the first line of the data file. For
contains the column names, and for COPY FROM, the first line is <command>COPY TO</>, the first line contains the column names,
ignored. and for <command>COPY FROM</>, the first line is ignored.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
On Win32, display better sub-second precision in EXPLAIN ANALYZE (Magnus) On Win32, display better sub-second precision in
<command>EXPLAIN ANALYZE</> (Magnus)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add trigger duration display to EXPLAIN ANALYZE (Tom) Add trigger duration display to <command>EXPLAIN ANALYZE</>
(Tom)
</para> </para>
<para> <para>
Prior releases lumped trigger execution time into the total execution Prior releases accumulated trigger execution time as part of the
time. total execution time.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for \x hex escapes in COPY (Sergey Ten) Add support for <literal>\x</> hex escapes in <command>COPY</>
(Sergey Ten)
</para> </para>
<para> <para>
Previous releases only supported octal escapes. Previous releases only supported octal escapes.
...@@ -760,35 +802,39 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -760,35 +802,39 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Have SHOW ALL include variable descriptions (Matthias Schmidt) Have <command>SHOW ALL</> include variable descriptions
(Matthias Schmidt)
</para> </para>
<para> <para>
SHOW varname still only displays the variable's value and does not <command>SHOW</> varname still only displays the variable's
include the description. value and does not include the description.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Have initdb create new standard database called "postgres" and Have initdb create new standard database called
convert utilities to use "postgres" rather than "template1" for <literal>postgres</> and convert utilities to use
<literal>postgres</> rather than <literal>template1</> for
standard lookups (Dave) 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
connection for utilities like createuser, and as a template for connection for utilities like createuser, and as a template for
new databases. This caused CREATE DATABASE to sometimes fail new databases. This caused <command>CREATE DATABASE</> to
because a new database cannot be created if anyone else is in sometimes fail because a new database cannot be created if
the template database. With this change, the default connection anyone else is in the template database. With this change, the
database is now 'postgres', meaning it is much less likely default connection database is now <literal>postgres</>, meaning
someone will be using template1 during CREATE DATABASE. it is much less likely someone will be using
<literal>template1</> during <command>CREATE DATABASE</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Create new reindexdb command-line utility by moving /contrib/reindexdb Create new reindexdb command-line utility by moving
into the server (Euler Taveira de Oliveira) <filename>/contrib/reindexdb</> into the server (Euler Taveira
de Oliveira)
</para> </para>
</listitem> </listitem>
...@@ -802,7 +848,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -802,7 +848,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add MAX() and MIN() aggregates for array types (Koju Iijima) Add <function>MAX()</> and <function>MIN()</> aggregates for
array types (Koju Iijima)
</para> </para>
<para> <para>
How does this work? How does this work?
...@@ -811,130 +858,138 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -811,130 +858,138 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Fix to_date() and to_timestamp() to behave reasonably when Fix <function>to_date()</> and <function>to_timestamp()</> to
CC and YY fields are both used (Karel Zak) behave reasonably when <literal>CC</> and <literal>YY</> fields
are both used (Karel Zak)
</para> </para>
<para> <para>
If the format specification contains CC and a year specification is If the format specification contains <literal>CC</> and a year
YYY or longer, ignore the CC. If the year specification is specification is <literal>YYY</> or longer, ignore the
YY or shorter, interpret CC as the previous century. ? <literal>CC</>. If the year specification is <literal>YY</> or
shorter, interpret <literal>CC</> as the previous century. ?
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add md5(bytea) (Abhijit Menon-Sen) Add <function>md5(bytea)</> (Abhijit Menon-Sen)
</para> </para>
<para> <para>
md5(text) already existed. <function>md5(text)</> already existed.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Fix CHAR() to properly pad out to the specified length when Fix <type>CHAR()</> to properly pad spaces to the specified
using a multiple-byte character set (Yoshiyuki Asaba) length when using a multiple-byte character set (Yoshiyuki
Asaba)
</para> </para>
<para> <para>
In prior releases, the padding of CHAR() was incorrect because it only In prior releases, the padding of <type>CHAR()</> was incorrect
padded to the specified number of bytes without considering how many because it only padded to the specified number of bytes without
characters were stored. considering how many characters were stored.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for NUMERIC ^ NUMERIC based on power(numeric, numeric) Add support for <command>NUMERIC ^ NUMERIC</> based on
<function>power(numeric, numeric)</>
</para> </para>
<para> <para>
The function already existed, but there was no operator assigned to The function already existed, but there was no operator assigned
it. to it.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Fix NUMERIC modulus by properly truncating the quotient during Fix <type>NUMERIC</> modulus by properly truncating the quotient
computation (Bruce) during computation (Bruce)
</para> </para>
<para> <para>
In previous releases, modulus for large values sometimes returned In previous releases, modulus for large values sometimes
negative results due to the rounding of the quotient. returned negative results due to the rounding of the quotient.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add a function lastval(), which returns the value returned by the Add a function <function>lastval()</>(Dennis Björklund)
last nextval() or setval() performed by the current session. (Dennis
Björklund)
</para> </para>
<para> <para>
lastval() is a simplified version of currval(). It automatically <function>lastval()</> is a simplified version of
determines the proper sequence name based on the most recent <function>currval()</>. It automatically determines the proper
nextval() call. sequence name based on the most recent <function>nextval()</> or
<function>setval()</> call performed by the current session.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add to_timestamp(double precision) Add <function>to_timestamp(DOUBLE PRECISION)</>
</para> </para>
<para> <para>
Converts Unix seconds since 1970 to a timestamp with timezone. Converts Unix seconds since 1970 to a <type>TIMESTAMP WITH
TIMEZONE</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add pg_postmaster_start_time() function (Euler Taveira de Oliveira, Add <function>pg_postmaster_start_time()</> function (Euler
Matthias Schmidt) Taveira de Oliveira, Matthias Schmidt)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow the full use of time zone names in "AT TIME ZONE", not just Allow the full use of time zone names in <command>AT TIME
the short list previously available (Magnus) ZONE</>, not just the short list previously available (Magnus)
</para>
<para>
Previously, only a predefined list of time zone names were supported
by AT TIME ZONE. Now any supported time zone name can be used, e.g.:
</para> </para>
<para> <para>
Previously, only a predefined list of time zone names were
supported by <command>AT TIME ZONE</>. Now any supported time
zone name can be used, e.g.:
<programlisting>
SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London'; SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
</programlisting>
In the above query, the daylight savings time rules were in effect on In the above query, the time zone used is adjusted based on the
that date are used. daylight savings time rules that were in effect on the supplied
date.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <function>GREATEST()</> and <function>LEAST()</> functions
Add Oracle-compatible GREATEST and LEAST functions (Pavel Stehule) (Pavel Stehule)
</para> </para>
<para> <para>
These functions take a variable number of arguments and return the These functions take a variable number of arguments and return
greatest or least value. the greatest or least value.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add pg_column_size() to return storage size of a column, including Add <function>pg_column_size()</> (Mark Kirkwood)
possible compression (Mark Kirkwood) </para>
<para>
This returns storage size of a column, including any
compression used.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add regexp_replace() (Atsushi Ogawa) Add <function>regexp_replace()</> (Atsushi Ogawa)
</para> </para>
<para> <para>
This allows regular expression replacement, like sed. A four-argument This allows regular expression replacement, like sed. A
version also allows for global (replace all) and case-insensitive four-argument version also allows for global (replace all) and
modes. case-insensitive modes.
</para> </para>
</listitem> </listitem>
...@@ -944,93 +999,138 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -944,93 +999,138 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
</para> </para>
<para> <para>
Previous versions sometimes returned unjustified results, like Previous versions sometimes returned unjustified results, like
'4 months'::interval / 5 returning '1 mon -6 days'. <command>'4 months'::interval / 5</> returning <command>'1 mon
-6 days'</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add internal 'day' field to INTERVAL so a 1 day interval can be Add an internal day field to <type>INTERVAL</> so a one day
distinguished from a 24 hour interval (Michael Glaesemann) interval can be distinguished from a 24 hour interval (Michael
Glaesemann)
</para> </para>
<para> <para>
Days that contain a daylight savings time adjustment are not 24 hours, Days that contain a daylight savings time adjustment are not 24
but typically 23 or 25 hours. This change allows days (not fixed hours, but typically 23 or 25 hours. This change allows days
24-hour periods) to be added to dates who's result includes a daylight (not fixed 24-hour periods) to be added to dates who's result
savings time adjustment period. Therefore, while in previous releases includes a daylight savings time adjustment period. Therefore,
'1 day' and '24 hours' where interchangeable interval periods, in this while in previous releases <literal>1 day</> and <literal>24
release they are treated differently, e.g. hours</> where interchangeable interval periods, in this release
they are treated differently, e.g.
<programlisting>
'2005-05-03 00:00:00 EST' + '1 day' = '2005-05-04 00:00:00-04'
'2005-05-03 00:00:00 EST' + '24 hours' = '2005-05-04 01:00:00-04'
</programlisting>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
'2005-05-03 00:00:00 EST' + '1 day' = '2005-05-04 00:00:00-04' Add <function>justify_days()</> and <function>justify_hours()</>
(Michael Glaesemann)
</para>
<para>
These functions, respectively, adjust days to an appropriate
number of full months and days, and adjust hours to an
appropriate number of full days and hours.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
'2005-05-03 00:00:00 EST' + '24 hours' = '2005-05-04 01:00:00-04' Move <filename>/contrib/dbsize</> into the backend, and rename
some of the functions (Dave Page, Andreas Pflug)
</para>
<para>
<itemizedlist>
<listitem>
<para>
<function>pg_tablespace_size()</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Move /contrib/dbsize into the backend, and rename some of the functions <function>pg_database_size()</>
(Dave Page, Andreas Pflug)
</para> </para>
</listitem>
<listitem>
<para>
<function>pg_relation_size()</>
</para>
</listitem>
<listitem>
<para> <para>
The new functions are: <function>pg_complete_relation_size()</>
pg_tablespace_size() </para>
pg_database_size() </listitem>
pg_relation_size()
pg_complete_relation_size() <listitem>
pg_size_pretty() <para>
<function>pg_size_pretty()</>
</para>
</listitem>
</itemizedlist>
</para> </para>
<para> <para>
complete_relation_size() includes indexes and TOAST tables. <function>complete_relation_size()</> includes indexes and TOAST
tables.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add justify_days() and justify_hours (Michael Glaesemann) Add functions for read-only file access to the cluster directory
(Dave Page, Andreas Pflug)
</para> </para>
<para> <para>
These functions, respectively, adjust days to an appropriate number of <itemizedlist>
full months and dayss, and adjust hours to an appropriate number
of full days and hours. <listitem>
<para>
<function>pg_stat_file()</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add files to do read-only I/O on the cluster directory (Dave Page, <function>pg_read_file()</>
Andreas Pflug) </para>
</listitem>
pg_stat_file() <listitem>
pg_read_file() <para>
pg_ls_dir() <function>pg_ls_dir()</>
</para>
</listitem>
</itemizedlist>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add pg_reload_conf() to force reloading of the configuration files (Dave Page, Add <function>pg_reload_conf()</> to force reloading of the
Andreas Pflug) configuration files (Dave Page, Andreas Pflug)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add pg_rotate_logfile() to force rotation of the server log file (Dave Page, Add <function>pg_rotate_logfile()</> to force rotation of the
server log file (Dave Page,
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Change pg_stat_* views to show TOAST tables (Tom) Change <literal>pg_stat_*</> views to show TOAST tables (Tom)
</para> </para>
</listitem> </listitem>
...@@ -1044,15 +1144,37 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1044,15 +1144,37 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Rename some encodings to be more consistent and to follow international Rename some encodings to be more consistent and to follow
standards(Bruce) international standards(Bruce)
</para>
<para>
<itemizedlist>
<listitem>
<para>
<literal>UNICODE</> is now <literal>UTF8</>
</para>
</listitem>
<listitem>
<para>
<literal>ALT</> is now <literal>WIN866</>
</para> </para>
</listitem>
<listitem>
<para>
<literal>WIN</> is now <literal>WIN1251</>
</para>
</listitem>
<listitem>
<para> <para>
Encoding name changes were: <literal>TCVN</> is now <literal>WIN1258</>
UNICODE is now UTF8 </para>
ALT is now WIN866 </listitem>
WIN is now WIN1251
TCVN is now WIN1258 </itemizedlist>
</para> </para>
<para> <para>
The original names still work. The original names still work.
...@@ -1061,23 +1183,26 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1061,23 +1183,26 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add support for Win1252 encoding (Roland Volkmann) Add support for <literal>WIN1252</> encoding (Roland Volkmann)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for 3 and 4-byte UTF8 characters (John Hansen) Add support for 3 and 4-byte <literal>UTF8</> characters (John
Hansen)
</para> </para>
<para> <para>
Previously only one and two-byte UTF8 characters were supported. Previously only one and two-byte <literal>UTF8</> characters
This is particularly important for support for some Chinese character. were supported. This is particularly important for support for
some Chinese character.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow direct conversion between EUC_JP and SJIS to improve performance (Atsushi Allow direct conversion between <literal>EUC_JP</> and
<literal>SJIS</> to improve performance (Atsushi
Ogawa) Ogawa)
</para> </para>
</listitem> </listitem>
...@@ -1092,14 +1217,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1092,14 +1217,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Fix ALTER LANGUAGE RENAME (Sergey Yatskevich) Fix <command>ALTER LANGUAGE RENAME</> (Sergey Yatskevich)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow function characteristics, like strictness and volatility, Allow function characteristics, like strictness and volatility,
to be modified via ALTER FUNCTION (Neil) to be modified via <command>ALTER FUNCTION</> (Neil)
</para> </para>
</listitem> </listitem>
...@@ -1111,14 +1236,17 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1111,14 +1236,17 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Allow SQL, plperl, PL/PgSQL functions to use OUT and INOUT parameters (Tom) Allow SQL, plperl, PL/PgSQL functions to use <command>OUT</> and
<command>INOUT</> parameters (Tom)
</para> </para>
<para> <para>
OUT is an alternate way for a function to return values. Instead of <command>OUT</> is an alternate way for a function to return
using RETURNS, the function's parameters can be specified as OUT or values. Instead of using <command>RETURNS</>, the function's
INOUT, allowing multiple values to be returned by the function. While parameters can be specified as <command>OUT</> or
returning multiple values from a function was possible in previous <command>INOUT</>, allowing multiple values to be returned by
releases, this greatly simplifies the process. the function. While returning multiple values from a function
was possible in previous releases, this greatly simplifies the
process.
</para> </para>
</listitem> </listitem>
...@@ -1134,54 +1262,58 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1134,54 +1262,58 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Reduce memory usage of PL/PgSQL functions (Neil) Reduce memory usage of PL/PgSQL functions (Neil)
</para> </para>
<para> <para>
Each function now has its own memory context that can be freed when Each function now has its own memory context that can be freed
the function exits. when the function exits.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Check function syntax as CREATE FUNCTION time, rather than at runtime Check function syntax as <command>CREATE FUNCTION</> time,
(Neil) rather than at runtime (Neil)
</para> </para>
<para> <para>
Previously, syntax errors were reported only when the function was Previously, syntax errors were reported only when the function
executed. was executed.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow OPEN to open non-SELECT queries like EXPLAIN and SHOW (Tom) Allow <command>OPEN</> to open non-<command>SELECT</> queries
like <command>EXPLAIN</> and <command>SHOW</> (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
No longer require functions to issue a RETURN statement (Tom) No longer require functions to issue a <command>RETURN</>
statement (Tom)
</para> </para>
<para> <para>
This is a byproduct of the newly added OUT and INOUT functionality. This is a byproduct of the newly added <command>OUT</> and
<command>INOUT</> functionality.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for an optional INTO clause to PL/PgSQL's EXECUTE command Add support for an optional <command>INTO</> clause to
(Pavel Stehule) PL/PgSQL's <command>EXECUTE</> command (Pavel Stehule)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Make CREATE TABLE AS set ROW_COUNT (Tom) Make <command>CREATE TABLE AS</> set <command>ROW_COUNT</> (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Define SQLSTATE and SQLERRM to return the SQLSTATE and Define <literal>SQLSTATE</> and <literal>SQLERRM</> to return
error message of the current exception (Pavel Stehule) the <literal>SQLSTATE</> and error message of the current
exception (Pavel Stehule)
</para> </para>
<para> <para>
These variables are only accessable inside exception blocks. These variables are only accessable inside exception blocks.
...@@ -1190,14 +1322,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1190,14 +1322,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Allow the parameters to the RAISE statement to be expressions Allow the parameters to the <command>RAISE</> statement to be
(Pavel Stehule) expressions (Pavel Stehule)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add a loop CONTINUE statement (Pavel Stehule) Add a loop <command>CONTINUE</> statement (Pavel Stehule)
</para> </para>
</listitem> </listitem>
...@@ -1217,11 +1349,12 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1217,11 +1349,12 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Allow large result sets to be returned efficiently (Abhijit Menon-Sen) Allow large result sets to be returned efficiently (Abhijit
Menon-Sen)
</para> </para>
<para> <para>
This allows functions to use return_next() to avoid building This allows functions to use <function>return_next()</> to avoid
the entire result set in memory. building the entire result set in memory.
</para> </para>
</listitem> </listitem>
...@@ -1230,15 +1363,16 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1230,15 +1363,16 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Allow one-row-at-a-time retrieval of query results (Abhijit) Allow one-row-at-a-time retrieval of query results (Abhijit)
</para> </para>
<para> <para>
This allows functions to use spi_query() and spi_fetchrow() to This allows functions to use <function>spi_query()</> and
avoid accumulating the entire result set in memory. <function>spi_fetchrow()</> to avoid accumulating the entire
result set in memory.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Force PL/Perl to handle strings as UTF8 if the server encoding is UTF8 Force PL/Perl to handle strings as <literal>UTF8</> if the
(David Kamholz) server encoding is <literal>UTF8</> (David Kamholz)
</para> </para>
</listitem> </listitem>
...@@ -1247,18 +1381,26 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1247,18 +1381,26 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Add a validator function for PL/Perl (Andrew) Add a validator function for PL/Perl (Andrew)
</para> </para>
<para> <para>
This allows syntax errors to be reported at definition time, rather This allows syntax errors to be reported at definition time,
than execution time. rather than execution time.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow PL/Perl to return a Perl array when the function returns an array Allow PL/Perl to return a Perl array when the function returns
type (Andrew) an array type (Andrew)
</para> </para>
<para> <para>
This basically maps PostgreSQL arrays to Perl arrays. This basically maps <productname>PostgreSQL</productname> arrays
to Perl arrays.
</para>
</listitem>
<listitem>
<para>
Allow Perl non-fatal warnings to generate <command>NOTICE</>
messages (Andrew)
</para> </para>
</listitem> </listitem>
...@@ -1272,17 +1414,20 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1272,17 +1414,20 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add psql \set ON_ERROR_ROLLBACK to allow statements in a transaction to Add psql <command>\set ON_ERROR_ROLLBACK</> to allow statements
error without affecting the rest of the transaction (Greg Sabino Mullane) in a transaction to error without affecting the rest of the
transaction (Greg Sabino Mullane)
</para> </para>
<para> <para>
This is basically implemented by wrapping every statement in a subtransaction. This is basically implemented by wrapping every statement in a
subtransaction.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for \x hex strings in psql variables (Bruce) Add support for <literal>\x</> hex strings in psql variables
(Bruce)
</para> </para>
<para> <para>
Octal escapes were already supported. Octal escapes were already supported.
...@@ -1291,14 +1436,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1291,14 +1436,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add psql support for troff "-ms" output format (Roger Leigh) Add psql support for <command>troff -ms</> output format (Roger
Leigh)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow psql's history file location to be controlled by HISTFILE (Andreas Allow psql's history file location to be controlled by
Seltenreich) <envar>HISTFILE</> (Andreas Seltenreich)
</para> </para>
<para> <para>
This allows configuration of per-database history storage. This allows configuration of per-database history storage.
...@@ -1307,14 +1453,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1307,14 +1453,14 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Prevent psql \x (expanded mode) from affecting other backslash output Prevent psql <command>\x</> (expanded mode) from affecting other
(Neil) backslash output (Neil)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add -L option to psql to log sessions (Lorne Sunley) Add <option>-L</> option to psql to log sessions (Lorne Sunley)
</para> </para>
<para> <para>
This option was added because some operating systems do not have This option was added because some operating systems do not have
...@@ -1324,31 +1470,33 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1324,31 +1470,33 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Have psql \d show tablespace of indexes (Qingqing Zhou) Have psql <command>\d</> show tablespace of indexes (Qingqing
Zhou)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow psql \h to make a best guess on the proper help information (Greg Allow psql help (<command>\h</>) to make a best guess on the
Sabino Mullane) proper help information (Greg Sabino Mullane)
</para> </para>
<para> <para>
This allows the user to just add \h to the front of the syntax error This allows the user to just add <command>\h</> to the front of
query and get help on the supported syntax. Previously any additional the syntax error query and get help on the supported syntax.
query text beyond the help topics supported had to be removed to use Previously any additional query text beyond the help topics
\h. supported had to be removed to use <command>\h</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add psql \pset numericlocale to allow numbers to be output in a Add psql <command>\pset numericlocale</> to allow numbers to be
locale-aware format (Eugen Nedelcu) output in a locale-aware format (Eugen Nedelcu)
</para> </para>
<para> <para>
For example, using C locale 100000 would be output as 100,000.0 and For example, using <literal>C</> locale <literal>100000</> would
European locale might output this value as 100.000,0. be output as <literal>100,000.0</> and European locale might
output this value as <literal>100.000,0</>.
</para> </para>
</listitem> </listitem>
...@@ -1362,7 +1510,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1362,7 +1510,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add -n / --schema switch to pg_restore (Richard van den Bergg) Add <option>-n</> / <option>--schema</> switch to pg_restore
(Richard van den Bergg)
</para> </para>
<para> <para>
This allows only objects from a specified schema to be restored. This allows only objects from a specified schema to be restored.
...@@ -1371,7 +1520,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1371,7 +1520,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Allow pg_dump to dump a consistent snapshot of large objects (Tom) Allow pg_dump to dump a consistent snapshot of large objects
(Tom)
</para> </para>
</listitem> </listitem>
...@@ -1389,12 +1539,12 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1389,12 +1539,12 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add --encoding to pg_dump (Magnus Hagander) Add <option>--encoding</> to pg_dump (Magnus Hagander)
</para> </para>
<para> <para>
This allows a database to be dumped in an encoding that is different This allows a database to be dumped in an encoding that is
from the server's encoding. This is valuable when transferring the dump different from the server's encoding. This is valuable when
to a machine with a different encoding. transferring the dump to a machine with a different encoding.
</para> </para>
</listitem> </listitem>
...@@ -1408,15 +1558,16 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1408,15 +1558,16 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add a "PGPASSFILE" environment variable to specify the password Add a <envar>PGPASSFILE</> environment variable to specify the
file's filename (Andrew Dunstan) password file's filename (Andrew Dunstan)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add lo_create(), that is similar to lo_creat() but allows the OID of the large Add <function>lo_create()</>, that is similar to
object to be specified (Tom) <function>lo_creat()</> but allows the OID of the large object
to be specified (Tom)
</para> </para>
</listitem> </listitem>
...@@ -1430,7 +1581,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1430,7 +1581,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add spinlock support for the Itanium processor using Intel compiler (Vikram Add spinlock support for the Itanium processor using Intel
compiler (Vikram
Kalsi) Kalsi)
</para> </para>
</listitem> </listitem>
...@@ -1449,20 +1601,22 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1449,20 +1601,22 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Rename Rendezvous to Bonjour to match OS/X feature renaming (Bruce) Rename Rendezvous to Bonjour to match OS/X feature renaming
(Bruce)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add support for wal_fsync_writethrough for Darwin (Chris Campbell) Add support for wal_fsync_writethrough for Darwin (Chris
Campbell)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Streamline the passing of information within the server, the optimizer, Streamline the passing of information within the server, the
and the lock system (Tom) optimizer, and the lock system (Tom)
</para> </para>
</listitem> </listitem>
...@@ -1471,7 +1625,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1471,7 +1625,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
Allow pg_config to be compiled using MSVC (Andrew Dunstan) Allow pg_config to be compiled using MSVC (Andrew Dunstan)
</para> </para>
<para> <para>
This is required to build DBD::Pg using MSVC. This is required to build DBD::Pg using <application>MSVC</>.
</para> </para>
</listitem> </listitem>
...@@ -1487,20 +1641,23 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1487,20 +1641,23 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Code cleanups (Coverity static analysis performed by EnterpriseDB) Code cleanups (Coverity static analysis performed by
EnterpriseDB)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Modify postgresql.conf to use documention defaults on/off rather Modify <filename>postgresql.conf</> to use documention defaults
than true/false (Bruce) <literal>on</>/<literal>off</> rather than
<literal>true</>/<literal>false</> (Bruce)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Enhance pg_config to be able to report more build-time values (Tom) Enhance <application>pg_config</> to be able to report more
build-time values (Tom)
</para> </para>
</listitem> </listitem>
...@@ -1514,7 +1671,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1514,7 +1671,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Add /contrib/pg_buffercache contrib module (Mark Kirkwood) Add <filename>/contrib/pg_buffercache</> contrib module (Mark
Kirkwood)
</para> </para>
<para> <para>
This displays the contents of the buffer cache, for debugging and This displays the contents of the buffer cache, for debugging and
...@@ -1524,25 +1682,28 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1524,25 +1682,28 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Remove /contrib/array because it is obsolete (Tom) Remove <filename>/contrib/array</> because it is obsolete (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Cleanup the contrib/lo module (Tom) Cleanup the <filename>/contrib/lo</> module (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Move /contrib/findoidjoins to src/tools (Tom) Move <filename>/contrib/findoidjoins</> to
<filename>/src/tools</> (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Remove the &lt;&lt, &gt;&gt;, &amp;&lt, and &amp;&gt; operators for contrib/cube Remove the <literal>&lt;&lt</>, <literal>&gt;&gt;</>,
<literal>&amp;&lt</>, and <literal>&amp;&gt;</> operators from
<filename>/contrib/cube</>
</para> </para>
<para> <para>
These operators were not useful. These operators were not useful.
...@@ -1551,26 +1712,62 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian ...@@ -1551,26 +1712,62 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.345 2005/08/23 14:54:06 momjian
<listitem> <listitem>
<para> <para>
Improve /contrib/btree_gist (Janko Richter) Improve <filename>/contrib/btree_gist</> (Janko Richter)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
/contrib/pgcrypto - Remove support for libmhash/libmcrypt (Marko Kreen) <filename>/contrib/pgcrypto</> - Remove support for
libmhash/libmcrypt (Marko Kreen)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
/contrib/pgcrypto - Add support for new encryption methods (Marko Kreen) <filename>/contrib/pgcrypto</> - Add support for new encryption
methods (Marko Kreen)
</para> </para>
<para> <para>
3des and AES <itemizedlist>
SHA2 (SHA256, SHA384, SHA512)
<listitem>
<para>
3DES
</para>
</listitem>
<listitem>
<para>
AES
</para>
</listitem>
<listitem>
<para>
Fortuna PRNG Fortuna PRNG
PGP encryption </para>
RSA key </listitem>
<listitem>
<para>
PGP
</para>
</listitem>
<listitem>
<para>
RSA
</para>
</listitem>
<listitem>
<para>
SHA2 (SHA256, SHA384, SHA512)
</para>
</listitem>
</itemizedlist>
</para> </para>
</listitem> </listitem>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment