open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Desultory copy-editing of the 9.3 release notes.

Browse Source 
I had time for a quick review of the notes, so here are some fixes.
pull/4/head
Tom Lane 13 years ago
parent 1d6c72a55b
commit f1ff90cfb1
1 changed files with 106 additions and 93 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 199
      doc/src/sgml/release-9.3.sgml

199
doc/src/sgml/release-9.3.sgml
Unescape View File

@ -13,11 +13,15 @@
<title>Overview</title> <title>Overview</title>
<para> <para>
ADD HERE Major enhancements include: Major enhancements include:
</para> </para>
<!-- This list duplicates items below, but without authors or details--> <!-- This list duplicates items below, but without authors or details-->
<para>
ADD HERE ...
</para>
<para> <para>
The above items are explained in more detail in the sections below. The above items are explained in more detail in the sections below.
</para> </para>
@ -129,9 +133,9 @@
</para> </para>
<para> <para>
Previously, <acronym>WAL</> files ending in <literal>FF</> were Previously, <acronym>WAL</> files with names ending in <literal>FF</>
not used. If you have <acronym>WAL</> backup or restore scripts were not used. If you have <acronym>WAL</> backup or restore scripts
that took that skipping into account, they need to be adjusted. that took that skipping into account, they will need to be adjusted.
</para> </para>
</listitem> </listitem>
@ -263,7 +267,7 @@
<listitem> <listitem>
<para> <para>
Add <link linkend="SQL-COPY"><command>COPY FREEZE</></link> Add <link linkend="SQL-COPY"><command>COPY FREEZE</></link>
option to avoid the overhead of later marking tuples as committed option to avoid the overhead of marking tuples as committed later
(Simon Riggs, Jeff Davis) (Simon Riggs, Jeff Davis)
</para> </para>
</listitem> </listitem>
@ -324,7 +328,7 @@
</para> </para>
<para> <para>
This reduces the statistics management read and write overhead. This reduces the I/O overhead for statistics tracking.
</para> </para>
</listitem> </listitem>
@ -443,8 +447,8 @@
<para> <para>
Instead, on Unix-like systems, <function>mmap()</> is used for Instead, on Unix-like systems, <function>mmap()</> is used for
shared memory. This eliminates the requirement of increasing shared memory. For most users, this will eliminate the need to
System V shared memory kernel parameters. adjust kernel parameters for shared memory.
</para> </para>
</listitem> </listitem>
@ -455,8 +459,8 @@
</para> </para>
<para> <para>
This renames configuration parameter The configuration parameter
<varname>unix_socket_directory</> to <link <varname>unix_socket_directory</> is replaced by <link
linkend="guc-unix-socket-directories"><varname>unix_socket_directories</></link>, linkend="guc-unix-socket-directories"><varname>unix_socket_directories</></link>,
which accepts a list of directories. which accepts a list of directories.
</para> </para>
@ -469,8 +473,8 @@
</para> </para>
<para> <para>
The directory is specified as <link Such a directory is specified with <link
linkend="config-includes"><varname>include_dir</></link> in server linkend="config-includes"><varname>include_dir</></link> in the server
configuration file. configuration file.
</para> </para>
</listitem> </listitem>
@ -484,9 +488,9 @@
</para> </para>
<para> <para>
This is the maximum value initdb attempts to set in <link This is the maximum value that initdb will attempt to set in <link
linkend="config-setting-configuration-file"><filename>postgresql.conf</></link>; linkend="config-setting-configuration-file"><filename>postgresql.conf</></link>;
the previous value was 32MB. the previous maximum was 32MB.
</para> </para>
</listitem> </listitem>
@ -571,6 +575,13 @@
to run on computers with different architectures (Heikki to run on computers with different architectures (Heikki
Linnakangas) Linnakangas)
</para> </para>
<para>
WAL files can still only be replayed on servers with the same
architecture as the primary; but they can now be transmitted to and
stored on machines of any architecture, since the
streaming replication protocol is now machine-independent.
</para>
</listitem> </listitem>
<listitem> <listitem>
@ -626,7 +637,8 @@
</para> </para>
<para> <para>
The new format is slightly more compact. The new format is slightly more compact, and is more efficient to
write.
</para> </para>
</listitem> </listitem>
@ -644,13 +656,13 @@
<listitem> <listitem>
<para> <para>
Implement <acronym>SQL</>-standard <link Implement <acronym>SQL</>-standard <link
linkend="queries-lateral"><literal>LATERAL</></link> for linkend="queries-lateral"><literal>LATERAL</></link> option for
<literal>FROM</>-clause subqueries and function calls (Tom Lane) <literal>FROM</>-clause subqueries and function calls (Tom Lane)
</para> </para>
<para> <para>
This is useful in allowing <literal>FROM</> subqueries and This feature allows subqueries and functions in <literal>FROM</> to
functions to reference output from tables in the <literal>FROM</> reference columns from other tables in the <literal>FROM</>
clause. The <literal>LATERAL</> keyword is optional for functions. clause. The <literal>LATERAL</> keyword is optional for functions.
</para> </para>
</listitem> </listitem>
@ -664,16 +676,6 @@
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Improve query string error location reporting (Tom Lane)
</para>
<para>
Only <command>CREATE SCHEMA ... IF NOT EXISTS</>? If so, remove it.
</para>
</listitem>
</itemizedlist> </itemizedlist>
</sect3> </sect3>
@ -685,19 +687,19 @@
<listitem> <listitem>
<para> <para>
Add support to <link linkend="event-triggers">event triggers</link> Add support for <link linkend="event-triggers">event triggers</link>
(Dimitri Fontaine, Robert Haas, &Aacute;lvaro Herrera) (Dimitri Fontaine, Robert Haas, &Aacute;lvaro Herrera)
</para> </para>
<para> <para>
This allows C functions to be called when specific commands are run. This allows C functions to be called when DDL commands are run.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow a multi-row <link Allow a multi-row <link
linkend="SQL-VALUES"><literal>VALUES</></link> clause in rules linkend="SQL-VALUES"><literal>VALUES</></link> clause in a rule
to reference <literal>OLD</>/<literal>NEW</> (Tom Lane) to reference <literal>OLD</>/<literal>NEW</> (Tom Lane)
</para> </para>
</listitem> </listitem>
@ -726,18 +728,20 @@
<listitem> <listitem>
<para> <para>
No longer output messages about implicit index and sequence creation (Robert Haas) Suppress messages about implicit index and sequence creation
(Robert Haas)
</para> </para>
<para> <para>
These messages now appear with <literal>DEBUG1</>-level output. These messages now appear at <literal>DEBUG1</> verbosity, so that
they will not be shown by default.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow <command>DROP TABLE IF NOT EXISTS</> to succeed for a Allow <command>DROP TABLE IF NOT EXISTS</> to succeed when a
non-existent schema (Bruce Momjian) non-existent schema is specified in the table name (Bruce Momjian)
</para> </para>
<para> <para>
@ -764,7 +768,7 @@
<para> <para>
This allows clients to retrieve table, column, data type, or constraint This allows clients to retrieve table, column, data type, or constraint
name error details. Previously such information had to be extracted from name error details. Previously such information had to be extracted from
error strings. Client language support is required to access these error strings. Client library support is required to access these
fields. fields.
</para> </para>
</listitem> </listitem>
@ -780,13 +784,13 @@
<listitem> <listitem>
<para> <para>
Add the <link linkend="SQL-ALTERTYPE"><command>ALTER TYPE ... IF Support <literal>IF NOT EXISTS</> option in <link
NOT EXISTS</></link> clause when adding enumerated type labels linkend="SQL-ALTERTYPE"><command>ALTER TYPE ... ADD VALUE</></link>
(Andrew Dunstan) (Andrew Dunstan)
</para> </para>
<para> <para>
This is useful for conditional label creation in transaction blocks. This is useful for conditionally adding values to enumerated types.
</para> </para>
</listitem> </listitem>
@ -822,16 +826,16 @@
<listitem> <listitem>
<para> <para>
Add a <link linkend="SQL-CREATEMATERIALIZEDVIEW">materialized Add <link linkend="SQL-CREATEMATERIALIZEDVIEW">materialized
view</link> relations (Kevin Grittner) views</link> (Kevin Grittner)
</para> </para>
<para> <para>
Unlike ordinary views, where the base tables are read on every access, Unlike ordinary views, where the base tables are read on every access,
materialized views create physical tables at creation or refresh time. materialized views create physical tables at creation or refresh time.
Access to the materialized view reads from these materialized physical Access to the materialized view then reads from its physical
tables. There is no facility for incrementally refreshing materialized table. There is not yet any facility for incrementally refreshing
views or auto-accessing them via base table access. materialized views or auto-accessing them via base table access.
</para> </para>
</listitem> </listitem>
@ -853,9 +857,16 @@
<listitem> <listitem>
<para> <para>
Allow views and rules to handle cases where referenced tables are Improve view/rule printing code to handle cases where referenced
renamed, or columns are renamed, added, or dropped (Tom Lane) tables are renamed, or columns are renamed, added, or dropped
HOW DOES IT HANDLE A DROPPED REFERENCED COLUMN? (Tom Lane)
</para>
<para>
Table and column renamings can produce cases where, if we merely
substitute the new name into the original text of a rule or view, the
result is ambiguous. This patch fixes the rule-dumping code to insert
table and column aliases if needed to preserve the original semantics.
</para> </para>
</listitem> </listitem>
@ -867,14 +878,7 @@
<para> <para>
Internally this is translated into <command>CREATE VIEW ... WITH Internally this is translated into <command>CREATE VIEW ... WITH
RECURSIVE</>. RECURSIVE ...</>.
</para>
</listitem>
<listitem>
<para>
When converting a table to a view, remove its system columns (Tom Lane)
KEEP?
</para> </para>
</listitem> </listitem>
@ -896,7 +900,8 @@
</para> </para>
<para> <para>
This change includes new libpq and server-side 64-bit-enabled functions. This change includes new libpq and server-side 64-bit-capable
large object access functions.
</para> </para>
</listitem> </listitem>
@ -1013,23 +1018,28 @@
<para> <para>
Cause <link Cause <link
linkend="functions-info-catalog-table"><function>pg_get_viewdef()</></link> linkend="functions-info-catalog-table"><function>pg_get_viewdef()</></link>
to default to wrapping after every <link to start a new line by default after each <link
linkend="SQL-SELECT"><command>SELECT</></link> target list and linkend="SQL-SELECT"><command>SELECT</></link> target list entry and
<literal>FROM</> entry (Marko Tiikkaja) <literal>FROM</> entry (Marko Tiikkaja)
</para> </para>
<para> <para>
This causes view output, like from <link This reduces line length in view printing, for instance in <link
linkend="APP-PGDUMP"><application>pg_dump</></link>, to be linkend="APP-PGDUMP"><application>pg_dump</></link> output.
more narrow.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Have <function>map_sql_value_to_xml_value()</> properly expand Fix <function>map_sql_value_to_xml_value()</> to print values of
domains (Pavel Stehule) WHAT IS THE USER-VISIBLE AFFECT HERE? domain types the same way their base type would be printed
map_sql_value_to_xml_value IS A C FUNCTION (Pavel Stehule)
</para>
<para>
There are special formatting rules for certain built-in types such as
<type>boolean</>; these rules now also apply to domains over these
types.
</para> </para>
</listitem> </listitem>
@ -1043,7 +1053,6 @@
<para> <para>
Previously functions already run in the current session ignored Previously functions already run in the current session ignored
<varname>search_path</> changes. <varname>search_path</> changes.
(Bruce Momjian)
</para> </para>
</listitem> </listitem>
@ -1074,11 +1083,12 @@
<listitem> <listitem>
<para> <para>
Allow PL/pgSQL to use <literal>RETURN</> with a composite-type Allow PL/pgSQL to use <literal>RETURN</> with a composite-type
expressions (Asif Rehman) expression (Asif Rehman)
</para> </para>
<para> <para>
Previously <literal>RETURN</> could only reference composite-type variables. Previously, in a function returning a composite type,
<literal>RETURN</> could only reference a variable of that type.
</para> </para>
</listitem> </listitem>
@ -1122,7 +1132,7 @@
<listitem> <listitem>
<para> <para>
Have PL/Python convert oid values to a proper Python numeric type Make PL/Python convert OID values to a proper Python numeric type
(Peter Eisentraut) (Peter Eisentraut)
</para> </para>
</listitem> </listitem>
@ -1130,7 +1140,7 @@
<listitem> <listitem>
<para> <para>
Handle <link linkend="spi"><acronym>SPI</></link> errors raised Handle <link linkend="spi"><acronym>SPI</></link> errors raised
explicitly with PL/Python's <literal>RAISE</> the same as as explicitly (with PL/Python's <literal>RAISE</>) the same as
internal <acronym>SPI</> errors (Oskari Saarenmaa and Jan Urbanski) internal <acronym>SPI</> errors (Oskari Saarenmaa and Jan Urbanski)
</para> </para>
</listitem> </listitem>
@ -1167,7 +1177,7 @@
<para> <para>
This is similar to the <link This is similar to the <link
linkend="APP-PGDUMP"><application>pg_dump</></link> <option>--table</> linkend="APP-PGDUMP"><application>pg_dump</></link> <option>--table</>
support. option.
</para> </para>
</listitem> </listitem>
@ -1175,7 +1185,7 @@
<para> <para>
Add <option>--dbname</> option to <link Add <option>--dbname</> option to <link
linkend="APP-PG-DUMPALL"><application>pg_dumpall</></link>, <link linkend="APP-PG-DUMPALL"><application>pg_dumpall</></link>, <link
linkend="app-pgbasebackup"><application>pg_basebackup</></link>, linkend="app-pgbasebackup"><application>pg_basebackup</></link>, and
<link <link
linkend="app-pgreceivexlog"><application>pg_receivexlog</></link> linkend="app-pgreceivexlog"><application>pg_receivexlog</></link>
to specify the connection string (Amit Kapila) to specify the connection string (Amit Kapila)
@ -1289,12 +1299,13 @@
<listitem> <listitem>
<para> <para>
Properly reset state if <application>psql</>'s <quote>\g file</> Properly reset state if the SQL command executed with
command failed (Tom Lane) <application>psql</>'s <quote>\g file</> fails (Tom Lane)
</para> </para>
<para> <para>
Previously failed commands discarded output from subsequent commands. Previously, the output from subsequent SQL commands would unexpectedly
continue to go to the same file.
</para> </para>
</listitem> </listitem>
@ -1314,7 +1325,7 @@
</para> </para>
<para> <para>
Longtable allows tables to span multiple pages. This format allows tables to span multiple pages.
</para> </para>
</listitem> </listitem>
@ -1352,14 +1363,14 @@
<listitem> <listitem>
<para> <para>
Add <application>pg_dump</> <option>--jobs</> to dump in parallel Add <application>pg_dump</> <option>--jobs</> option to dump tables in
when using directory output format (Joachim Wieland) parallel (Joachim Wieland)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Have <application>pg_dump</> output functions in a predictable Have <application>pg_dump</> output functions in a more predictable
order (Joel Jacobson) order (Joel Jacobson)
</para> </para>
</listitem> </listitem>
@ -1417,7 +1428,7 @@
<listitem> <listitem>
<para> <para>
Have initdb issue a warning about placing the data directory at the Have initdb issue a warning about placing the data directory at the
top of file system mount points (Bruce Momjian) top of a file system mount point (Bruce Momjian)
</para> </para>
</listitem> </listitem>
@ -1550,14 +1561,13 @@
<listitem> <listitem>
<para> <para>
Add <function>Assert()</> functionality to client-side code for Support <function>Assert()</> in client-side code (Andrew Dunstan)
frontend code (Andrew Dunstan)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Change many internal many backend functions to return <type>OID</>s Change many internal backend functions to return <type>OID</>s
rather than void (Dimitri Fontaine) rather than void (Dimitri Fontaine)
</para> </para>
@ -1668,9 +1678,9 @@
<listitem> <listitem>
<para> <para>
Allow write-enabled <link Allow <link linkend="SQL-CREATEFOREIGNDATAWRAPPER">foreign data
linkend="SQL-CREATEFOREIGNDATAWRAPPER">foreign data wrappers</link> wrappers</link> to support writes (inserts/updates/deletes) on foreign
to support writes (KaiGai Kohei) tables (KaiGai Kohei)
</para> </para>
</listitem> </listitem>
@ -1681,7 +1691,7 @@
</para> </para>
<para> <para>
This foreign data wrapper allows writes. This foreign data wrapper supports writes.
</para> </para>
</listitem> </listitem>
@ -1695,7 +1705,7 @@
<listitem> <listitem>
<para> <para>
Add support for indexing of regular-expression searches in Add support for indexing of regular-expression searches in
extension <link linkend="pgtrgm"><productname>pg_trgm</></link> <link linkend="pgtrgm"><productname>pg_trgm</></link>
(Alexander Korotkov) (Alexander Korotkov)
</para> </para>
</listitem> </listitem>
@ -1821,26 +1831,27 @@
<listitem> <listitem>
<para> <para>
Add <option>--foreign-keys</> option to <application>pgbench</> (Jeff Janes) Add <option>--foreign-keys</> option to <application>pgbench</>
(Jeff Janes)
</para> </para>
<para> <para>
This adds foreign key constraints to tables, for use in foreign This adds foreign key constraints to the standard tables created by
key performance testing. <application>pgbench</>, for use in foreign key performance testing.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow <application>pgbench</> to aggregate performance statistics Allow <application>pgbench</> to aggregate performance statistics
and produce output every <option>--aggregate-interval</> specified and produce output every <option>--aggregate-interval</>
seconds (Tomas Vondra) seconds (Tomas Vondra)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <application>pg_bench</> <option>--sampling-rate</> option Add <application>pgbench</> <option>--sampling-rate</> option
to control the percentage of transactions logged (Tomas Vondra) to control the percentage of transactions logged (Tomas Vondra)
</para> </para>
</listitem> </listitem>
@ -1858,10 +1869,12 @@
Add <application>pgbench</> <option>-q</> mode to print one output Add <application>pgbench</> <option>-q</> mode to print one output
line every five seconds (Tomas Vondra) line every five seconds (Tomas Vondra)
</para> </para>
</listitem>
<listitem>
<para> <para>
Output <application>pgbench</> elapsed and estimated remaining Output <application>pgbench</> elapsed and estimated remaining
time during initialization logging (Tomas Vondra) time during initialization (Tomas Vondra)
</para> </para>
</listitem> </listitem>

Write Preview
Loading…
Cancel
Save