mirror of
https://github.com/postgres/postgres.git
synced 2025-06-08 22:02:03 +03:00
Wordsmith improvements to first half of release notes, move TEXT cast
item to #1 imcompatibility slot.
This commit is contained in:
parent
fbab505216
commit
b13602c6d0
@ -1,4 +1,4 @@
|
|||||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.543 2007/11/17 15:17:16 momjian Exp $ -->
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.544 2007/11/17 21:13:42 momjian Exp $ -->
|
||||||
<!--
|
<!--
|
||||||
|
|
||||||
Typical markup:
|
Typical markup:
|
||||||
@ -160,13 +160,13 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Asynchronous commit delays writes to WAL for committed transactions
|
Asynchronous commit delays writes to WAL during transaction commit
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Distributed checkpoints prevent I/O spikes during checkpoints
|
Distributed checkpoints prevent checkpoint I/O spikes
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -192,8 +192,8 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Prevent large sequential scans from forcing out more frequently
|
Prevent large sequential scans from forcing out more frequently used
|
||||||
used cached pages
|
cached pages
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -212,7 +212,7 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Reduce need for vacuum by using pseudo-transaction ids in
|
Reduce need for vacuum by using non-persistent transaction ids for
|
||||||
read-only transactions
|
read-only transactions
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
@ -236,18 +236,6 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
<filename>contrib/tsearch2</> features have been moved into
|
|
||||||
the core server, with some minor syntax changes
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>
|
|
||||||
<filename>contrib/tsearch2</> now contains a compatibility
|
|
||||||
interface.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Non-character values are no longer automatically cast to
|
Non-character values are no longer automatically cast to
|
||||||
@ -256,18 +244,10 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
Previously, a function or operator that took a <type>TEXT</>
|
Previously, a function or operator that took a <type>TEXT</>
|
||||||
parameter used to automatically cast a non-<type>TEXT</> value to
|
parameter automatically cast a non-<type>TEXT</> value to
|
||||||
<type>TEXT</> and call the function or operator, if needed. This
|
<type>TEXT</>, if needed. This no longer happens and an explicit
|
||||||
no longer happens and an explicit cast to <type>TEXT</> is now
|
cast to <type>TEXT</> is now required. For example, these
|
||||||
required. For example, these expressions now throw an error:
|
expressions now require a cast to TEXT:
|
||||||
|
|
||||||
<programlisting>
|
|
||||||
substr(current_date, 1, 1);
|
|
||||||
23 LIKE '%2%'
|
|
||||||
5.4 ~ '6';
|
|
||||||
</programlisting>
|
|
||||||
|
|
||||||
but these work because of the explicit casts:
|
|
||||||
|
|
||||||
<programlisting>
|
<programlisting>
|
||||||
substr(current_date::text, 1, 1);
|
substr(current_date::text, 1, 1);
|
||||||
@ -287,6 +267,18 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Full text search features from <filename>contrib/tsearch2</> have
|
||||||
|
been moved into the core server, with some minor syntax changes
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
<filename>contrib/tsearch2</> now contains a compatibility
|
||||||
|
interface.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Numerous changes in administrative server parameters
|
Numerous changes in administrative server parameters
|
||||||
@ -333,7 +325,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<para>
|
<para>
|
||||||
<literal>ORDER BY ... USING</> <replaceable>operator</> now must
|
<literal>ORDER BY ... USING</> <replaceable>operator</> now must
|
||||||
use a less-than or greater-than <replaceable>operator</> that is
|
use a less-than or greater-than <replaceable>operator</> that is
|
||||||
defined in a btree operator class (???)
|
defined in a btree operator class
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -351,19 +343,19 @@ substr(current_date::text, 1, 1);
|
|||||||
The old naming convention is still honored when possible, but
|
The old naming convention is still honored when possible, but
|
||||||
client code should no longer depending on it. Application code
|
client code should no longer depending on it. Application code
|
||||||
should use the new <literal>pg_type.typarray</literal> column to
|
should use the new <literal>pg_type.typarray</literal> column to
|
||||||
determine the array data type.
|
determine the array's data type.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<command>SET LOCAL</command> changes now persist until
|
<command>SET LOCAL</command> changes now persist until
|
||||||
the end of the top-most transaction, unless rolled back (Tom)
|
the end of the outer-most transaction, unless rolled back (Tom)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Previously <command>SET LOCAL</command>'s effects reverted
|
Previously <command>SET LOCAL</command>'s effects were lost
|
||||||
during subtransaction commit and <command>RELEASE</>.
|
after subtransaction commit or <command>RELEASE</>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -374,7 +366,7 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
For example, <literal>BEGIN; DROP DATABASE; COMMIT</> will now be
|
For example, <literal>"BEGIN; DROP DATABASE; COMMIT"</> will now be
|
||||||
rejected even if submitted as a single query message.
|
rejected even if submitted as a single query message.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
@ -399,11 +391,11 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
In UTF8-encoded databases the argument is now processed as a Unicode
|
In UTF8-encoded databases the <function>chr()</function> argument is
|
||||||
code point. In other multi-byte encodings the argument must designate
|
now processed as a Unicode code point. In other multi-byte encodings
|
||||||
a 7-bit ASCII character, or an error is raised. Zero also causes an
|
<function>chr()</function>'s argument must designate a 7-bit ASCII
|
||||||
error. <function>ascii()</function> has been adjusted as well to
|
character. Zero is no longer a valid parameter.
|
||||||
match this behavior.
|
<function>ascii()</function> has been adjusted similarly.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -425,7 +417,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<para>
|
<para>
|
||||||
<function>convert_from(bytea, name)</function> returns
|
<function>convert_from(bytea, name)</function> returns
|
||||||
<type>TEXT</> — converts the first argument from the named
|
<type>TEXT</> — converts the first argument from the named
|
||||||
encoding to the database encoding.
|
encoding to the database encoding
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -433,7 +425,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<para>
|
<para>
|
||||||
<function>convert_to(text, name)</function> returns
|
<function>convert_to(text, name)</function> returns
|
||||||
<type>BYTEA</> — converts the first argument from the
|
<type>BYTEA</> — converts the first argument from the
|
||||||
database encoding to the named encoding.
|
database encoding to the named encoding
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -441,7 +433,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<para>
|
<para>
|
||||||
<function>length(bytea, name)</function> returns
|
<function>length(bytea, name)</function> returns
|
||||||
<type>INTEGER</> — gives the length of the first
|
<type>INTEGER</> — gives the length of the first
|
||||||
argument in characters in the named encoding.
|
argument in characters in the named encoding
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
@ -496,8 +488,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<command>ROLLBACK</> outside a multi-statement transaction now
|
<command>ROLLBACK</> outside a multi-statement transaction now
|
||||||
issues a <literal>NOTICE</> instead of <literal>WARNING</> (Bruce)
|
issues <literal>NOTICE</> instead of <literal>WARNING</> (Bruce)
|
||||||
(Tom)
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -508,10 +499,10 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The new <function>SET_VARSIZE()</> macro <emphasis>must</> be
|
The new <function>SET_VARSIZE()</> macro <emphasis>must</> be used
|
||||||
used to set the length of generated values. Also, it might be
|
to set the length of generated <type>varlena</> values. Also, it
|
||||||
necessary to expand (<quote>de-TOAST</quote>) input values in
|
might be necessary to expand (<quote>de-TOAST</quote>) input values
|
||||||
additional places.
|
in more cases.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -533,36 +524,36 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Asynchronous commit delays writes to WAL for committed transactions
|
Asynchronous commit delays writes to WAL during transaction commit
|
||||||
(Simon)
|
(Simon)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This feature dramatically increases performance for data-modifying
|
This feature dramatically increases performance for data-modifying
|
||||||
queries. The disadvantage is that because on-disk changes are
|
queries. The disadvantage is that because disk writes are
|
||||||
delayed, if the operating system crashes before data is written to
|
delayed, if the operating system crashes before data is written to
|
||||||
the disk, committed data will be lost. This is useful only for
|
the disk, committed data will be lost. This feature is useful for
|
||||||
applications that can accept some data loss. Unlike
|
applications that can accept some data loss. Unlike
|
||||||
<varname>fsync</varname>, asynchronous commit does not risk database
|
<varname>fsync</varname>, asynchronous commit does not risk database
|
||||||
corruption; the worst case is that after an operating system crash
|
consistency; the worst case is that after an operating system crash
|
||||||
the last few reportedly-committed transactions will be missing.
|
the last few reportedly-committed transactions might be missing.
|
||||||
This feature is enabled turning <varname>synchronous_commit</>
|
This feature is enabled by turning <varname>synchronous_commit</>
|
||||||
<literal>off</> and setting <varname>wal_writer_delay</>.
|
<literal>off</> and setting <varname>wal_writer_delay</>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Distributed checkpoints prevent I/O spikes during
|
Distributed checkpoints prevent checkpoint I/O spikes (Itagaki
|
||||||
checkpoints (Itagaki Takahiro and Heikki Linnakangas)
|
Takahiro and Heikki Linnakangas)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Previously all modified buffers were forced to disk at
|
Previously all modified buffers were forced to disk during
|
||||||
checkpoint time, causing an I/O spike and decreasing server
|
checkpoints, causing an I/O spike and decreasing server performance.
|
||||||
performance. This new capability spreads checkpoint activity out
|
This new capability spreads disk writes out between checkpoints,
|
||||||
between checkpoints, reducing peak I/O usage. (User-requested
|
reducing peak I/O usage. (User-requested and shutdown checkpoints
|
||||||
and shutdown checkpoints are still immediately written to disk.)
|
are still written immediately to disk.)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -573,14 +564,14 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
To allow high concurrency <command>UPDATE</> creates a new tuple,
|
To allow high concurrency <command>UPDATE</>, creates a new tuple
|
||||||
rather than replacing the old tuple. Previously only
|
rather than overwriting the old tuple. Previously only
|
||||||
<command>VACUUM</> could reuse space taken by old tuples. With
|
<command>VACUUM</> could reuse space taken by old tuples. With
|
||||||
<acronym>HOT</> dead tuple space can be reused at the time of
|
<acronym>HOT</> dead tuple space can be reused at the time of
|
||||||
<command>UPDATE</> or <command>INSERT</>. This allows for more
|
<command>UPDATE</> or <command>INSERT</>. This allows for more
|
||||||
consistent performance. <acronym>HOT</> even allows deleted row
|
consistent performance. <acronym>HOT</> even allows deleted row
|
||||||
space reuse. <acronym>HOT</> space reuse is not possible if
|
space reuse. <acronym>HOT</> space reuse is not possible for
|
||||||
<command>UPDATE</> changes indexed columns.
|
<command>UPDATE</>s that change indexed columns.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -602,24 +593,24 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
Variable-length data types with data values less then 128 bytes
|
Variable-length data types with data values less then 128 bytes
|
||||||
will see a decrease of 3-6 bytes. For example, two
|
will see a storage decrease of 3-6 bytes. For example, two
|
||||||
<type>CHAR(1)</type> fields now take 4 bytes instead of 16. Rows
|
<type>CHAR(1)</type> fields now use 4 bytes instead of 16. Rows
|
||||||
are also 4 bytes shorter.
|
are also 4 bytes shorter.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Reduce need for vacuum by using pseudo-transaction ids in
|
Reduce need for vacuum by using non-persistent transaction ids for
|
||||||
read-only transactions (Florian Pflug)
|
read-only transactions (Florian Pflug)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Pseudo-transaction ids do not increment the global transaction
|
Non-persistent transaction ids do not increment the global
|
||||||
counter. Therefore, they do not add to the need for vacuum to
|
transaction counter. Therefore, they do not add to the need for
|
||||||
read all database rows to prevent problems with transaction id
|
vacuum to read all database rows to prevent problems with
|
||||||
wrap-around. Other transaction performance improvements were also
|
transaction id wrap-around. Other transaction performance
|
||||||
made that should improve concurrency.
|
improvements were also made that should improve concurrency.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -637,10 +628,12 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Unless WAL archiving is enabled, it is possible to just
|
Unless WAL archiving is enabled, the system now avoids WAL writes
|
||||||
<function>fsync()</> the table at the end of the command,
|
for <command>CLUSTER</command> and just <function>fsync()</>s the
|
||||||
increasing performance. Additional WAL efficiencies were also
|
table at the end of the command. It also does the same for
|
||||||
made.
|
<command>COPY</command> if the table was created in the same
|
||||||
|
transaction. Additional WAL efficiencies for these commands were
|
||||||
|
also made.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -659,9 +652,9 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
This is accomplished by starting the new sequential scan in the
|
This is accomplished by starting the new sequential scan in the
|
||||||
middle of the table (where the other sequential scan is already
|
middle of the table (where another sequential scan is already
|
||||||
in-progress) and wrapping around to the beginning to finish. This
|
in-progress) and wrapping around to the beginning to finish. This
|
||||||
may affect the order of returned rows in a non-<literal>ORDER BY</>
|
can affect the order of returned rows in a non-<literal>ORDER BY</>
|
||||||
query.
|
query.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
@ -675,7 +668,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<para>
|
<para>
|
||||||
This is done by sequentially scanning the table and using a filter
|
This is done by sequentially scanning the table and using a filter
|
||||||
to save the few requested rows, rather than sorting the entire
|
to save the few requested rows, rather than sorting the entire
|
||||||
table. This is used if there is no matching index.
|
table. This is useful if there is no matching index.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -701,26 +694,26 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Support multiple concurrent autovacuum processes (Alvaro, Itagaki
|
Autovacuum is now enabled by default (Alvaro)
|
||||||
Takahiro)
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>
|
|
||||||
This allows multiple vacuums to run concurrently, meaning
|
|
||||||
vacuuming of a large table will not prevent smaller tables from
|
|
||||||
being vacuumed at the same time. Autovacuum is now considered
|
|
||||||
mature and thus enabled by default. Several autovacuum
|
|
||||||
default parameter values were also updated.
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Autovacuum is now enabled by default (Alvaro)
|
Support multiple concurrent autovacuum processes (Alvaro, Itagaki
|
||||||
|
Takahiro)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Also, autovacuum now reports its activity start time in
|
This allows multiple vacuums to run concurrently. This prevents
|
||||||
|
vacuuming of a large table from delaying the vacumming of smaller
|
||||||
|
tables. Several autovacuum parameter defaults were also modified.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Autovacuum now reports its activity start time in
|
||||||
<literal>pg_stat_activity</literal> (Tom)
|
<literal>pg_stat_activity</literal> (Tom)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
@ -752,8 +745,8 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This should be used in place of the native Kerberos authentication
|
This should be preferred to native Kerberos authentication because
|
||||||
because it is an industry standard.
|
GSSAPI is an industry standard.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -783,14 +776,14 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
JOHAB cannot safely be used as a server-side encoding.
|
JOHAB is not safe as a server-side encoding.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Allow logfile creation in CSV format (Arul Shaji, Greg Smith,
|
Allow server log output in comma-separated value (CSV) format (Arul
|
||||||
Andrew Dunstan)
|
Shaji, Greg Smith, Andrew Dunstan)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -801,21 +794,21 @@ substr(current_date::text, 1, 1);
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add <varname>log_autovacuum_min_duration</varname> parameter to
|
Add <varname>log_autovacuum_min_duration</varname> parameter to
|
||||||
support configurable logging of autovacuum actions (Simon, Alvaro)
|
support configurable logging of autovacuum activity (Simon, Alvaro)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add <varname>log_lock_waits</varname> parameter to log long wait
|
Add <varname>log_lock_waits</varname> parameter to log lock waiting
|
||||||
times (Simon)
|
(Simon)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add <varname>log_temp_files</varname> parameter to log usage of
|
Add <varname>log_temp_files</varname> parameter to log temporary
|
||||||
temporary files (Bill Moran)
|
file usage (Bill Moran)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -828,16 +821,21 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<varname>log_line_prefix</varname> escapes <literal>%s</literal>
|
<varname>log_line_prefix</varname> now supports
|
||||||
and <literal>%c</literal> can now be used in all processes
|
<literal>%s</literal> and <literal>%c</literal> escapes in all
|
||||||
(Andrew)
|
processes (Andrew)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Previously these escapes worked only for user sessions, not for
|
||||||
|
database helper processes.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Use our own timezone support for formatting timestamps displayed in
|
Use PostgreSQL-supplied timezone support for formatting timestamps
|
||||||
the server log (Tom)
|
displayed in the server log (Tom)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -868,10 +866,10 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Previously setting <varname>archive_command</> to an empty
|
Previously setting <varname>archive_command</> to an empty string
|
||||||
string turned off archiving. Now <varname>archive_mode</> turns
|
turned off archiving. Now <varname>archive_mode</> turns archiving
|
||||||
archiving on and off. This is useful for stopping archiving
|
on and off, independent of <varname>archive_command</>. This is
|
||||||
temporarily.
|
useful for stopping archiving temporarily.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -892,8 +890,8 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add <varname>log_restartpoints</varname> archive recovery option
|
Add <varname>log_restartpoints</varname> to control logging of
|
||||||
to emit a log message at each recovery restart point (Simon)
|
every point-in-time recovery restart point (Simon)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -912,19 +910,19 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This parameters allows a list of tablespaces to be specified
|
This parameters supports a list of tablespaces to be used. This
|
||||||
which enables spreading the I/O load across multiple
|
enables spreading the I/O load across multiple tablespaces. A random
|
||||||
tablespaces. A random tablespace is chosen each time a temporary
|
tablespace is chosen each time a temporary object is created.
|
||||||
object is created. Temporary files are not stored in
|
Temporary files are no longer stored in per-database
|
||||||
per-database <filename>pgsql_tmp/</filename> directories anymore
|
<filename>pgsql_tmp/</filename> directories but in per-tablespace
|
||||||
but in per-tablespace directories.
|
directories.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
New system view <literal>pg_stat_bgwriter</literal> displays
|
New system view <literal>pg_stat_bgwriter</literal> displays
|
||||||
statistics about the background writer activity (Magnus)
|
statistics about background writer activity (Magnus)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -937,7 +935,7 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add an <literal>xact_start</literal> column to
|
Add an <literal>xact_start</literal> (transaction start time) column to
|
||||||
<literal>pg_stat_activity</literal> (Neil)
|
<literal>pg_stat_activity</literal> (Neil)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
@ -960,8 +958,8 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
We now always start the collector process, unless prevented by a
|
We now always start the collector process, unless <acronym>UDP</>
|
||||||
problem with setting up the stats UDP socket.
|
socket creation fails.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -979,8 +977,9 @@ substr(current_date::text, 1, 1);
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Merge <varname>stats_block_level</> and <varname>stats_row_level</>
|
Merge <varname>stats_block_level</> and <varname>stats_row_level</>
|
||||||
parameters into a single parameter <varname>track_counts</>,
|
parameters into a single parameter <varname>track_counts</>, which
|
||||||
which controls all messages sent to the collector process (Tom)
|
controls all messages sent to the statistics collector process
|
||||||
|
(Tom)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -999,7 +998,7 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
Previously, dropping (or attempting to drop) a user who owned many
|
Previously, dropping (or attempting to drop) a user who owned many
|
||||||
objects could result in extremely large <literal>NOTICE</literal> or
|
objects could result in large <literal>NOTICE</literal> or
|
||||||
<literal>ERROR</literal> messages listing all these objects; this
|
<literal>ERROR</literal> messages listing all these objects; this
|
||||||
caused problems for some client applications. The length of the
|
caused problems for some client applications. The length of the
|
||||||
list is now limited, although a full list is still sent to the
|
list is now limited, although a full list is still sent to the
|
||||||
@ -1014,11 +1013,11 @@ substr(current_date::text, 1, 1);
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This allows low-level code to recognize that these tables are
|
This allows low-level code to recognize these tables as temporary,
|
||||||
temporary, which enables various optimizations such as not
|
which enables various optimizations such as not WAL-logging changes
|
||||||
WAL-logging changes and using local rather than shared buffers
|
and using local rather than shared buffers for access. This also
|
||||||
for access. This also fixes a bug where backends unexpectedly
|
fixes a bug where backends unexpectedly held open file references
|
||||||
held open file references to temporary tables.
|
to temporary tables.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -1026,7 +1025,7 @@ substr(current_date::text, 1, 1);
|
|||||||
<para>
|
<para>
|
||||||
Fix problem that a constant flow of new connection requests could
|
Fix problem that a constant flow of new connection requests could
|
||||||
indefinitely delay the postmaster from completing a shutdown or
|
indefinitely delay the postmaster from completing a shutdown or
|
||||||
crash restart (Tom)
|
a crash restart (Tom)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -1039,7 +1038,7 @@ substr(current_date::text, 1, 1);
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Add Kerberos realm specification, <varname>krb_realm</> (Magnus)
|
Add a Kerberos realm parameter, <varname>krb_realm</> (Magnus)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user