Re: pgsql: First pass over release documentation.

The overview descriptions were moved down to the body of the release
notes. As far as the uppercase of type names, I though most SQL code
uppercased them.

---------------------------------------------------------------------------

Neil Conway wrote:
> On Thu, 2007-10-18 at 05:15 +0000, Bruce Momjian wrote:
> > First pass over release documentation. I trimmed down some of the
> > entries and removed a few.
>
> Much of the information you've removed is useful, IMHO. For example:
>
> @@ -134,26 +119,12 @@ do it for earlier branch release files.
> <para>
> User-defined types can now have type modifiers
> </para>
> -
> - <para>
> - This allows a user type to take a modifier when
> - being referenced, e.g. <type>SSNUM(7)</>. Previously only
> - predefined system data types would allow this, e.g.
> - <type>CHAR(4)</>.
> - </para>
> </listitem>
>
> <listitem>
> <para>
> Automatically invalidate cached function code when table
> - definitions change
> - </para>
> -
> - <para>
> - Previously PL/PgSQL functions that referenced temporary tables
> - would fail if the temporary table was dropped and recreated
> - between function invocations, unless <literal>EXECUTE</> was
> - used.
> + definitions change or statistics are updated
> </para>
> </listitem>
>
> @@ -181,13 +148,6 @@ do it for earlier branch release files.
> <para>
> Multiple autovacuum worker processes, and other autovacuum improvements
> </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.
> - </para>
> </listitem>
>
> @@ -217,18 +177,6 @@ do it for earlier branch release files.
> Asynchronous commit option allows transactions to be committed
> but on-disk changes to be delayed
> </para>
> -
> - <para>
> - This feature dramatically increases performance for data
> - modification queries. The disadvantage is that because on-disk
> - changes are delayed, if the operating system crashes before data
> - is written to the disk, committed data will be lost. This is
> - useful only for applications that can accept some data loss.
> - Unlike <varname>fsync</varname>, asynchronous commit does not
> - risk database corruption; the worst case is that after an
> - operating system crash the last few reportedly-committed
> - transactions will be missing.
> - </para>
> </listitem>
>
> In other words, the changes to the "Overview" section are mostly regressions, IMHO.
>
> BTW, I'm not sure why you're uppercasing the names of data types -- they
> are lowercased in most of the rest of the SGML docs.
>
> -Neil
>

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +