Simon Riggs wrote:
> On Fri, 2006-09-15 at 15:37 -0400, Bruce Momjian wrote:
> > I have completed my first pass over the release notes and Tom has made
> > some additions:
> >
> > http://momjian.postgresql.org/cgi-bin/pgrelease
> >
> > I will probably go over them again in a few hours, update them to
> > current CVS, then move them into our SGML documentation by Monday.
>
> We talk about "standby point-in-time-recovery (PITR) servers" in the
> release notes, but in the docs PITR has now been replaced by Continuous
> Archiving and we talk about Warm Standby servers.
>
> Can we call them Warm Standby servers? That makes more sense for the
> general reader and matches the docs.
Agreed. Updated.
> Also, not sure what the thoughts are regarding surnames. I'm referred to
> as both Simon and Simon Riggs in the release notes. Should we have a
> policy of first mention uses full name, subsequent mentions just use
> first name if there is no confusion by doing so?
OK, changed to "Simon", but am open to making more wholesale changes.
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/release.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/release.sgml,v
retrieving revision 1.446
diff -c -c -r1.446 release.sgml
*** doc/src/sgml/release.sgml 20 Sep 2006 22:48:47 -0000 1.446
--- doc/src/sgml/release.sgml 21 Sep 2006 03:09:54 -0000
***************
*** 37,52 ****
<para>
This release adds many improvements to commands and database
! facilities that were requested by users. Rather than adding a
! few new features, this release makes many features from previous
! releases easier to use. For example, it is now much easier to
! create standby point-in-time-recovery (PITR) servers. Many
performance bottlenecks have been eliminated, allowing more
! functionality to be enabled by default. Various additions will
! make porting from other databases easier. The changes in this
! release continue the <productname>PostgreSQL</> tradition of
! being not only the most advanced open source database, but also
! the easiest to use.
</para>
</sect2>
--- 37,52 ----
<para>
This release adds many improvements to commands and database
! facilities that were requested by users. Rather than adding
! a few new features, this release makes many features from
! previous releases easier to use. For example, there are now
! additional controls for continuous archiving. Many
performance bottlenecks have been eliminated, allowing more
! functionality to be enabled by default. Various additions
! will make porting from other databases easier. The changes
! in this release continue the <productname>PostgreSQL</>
! tradition of being not only the most advanced open source
! database, but also the easiest to use.
</para>
</sect2>
***************
*** 489,509 ****
<listitem>
<para>
! Allow a forced switch to a new xlog file (Simon Riggs, Tom)
</para>
<para>
! This is valuable for keeping <acronym>PITR</> standby
! servers in sync with the master. xlog file switching also
! happens automatically during <function>pg_stop_backup()</>.
! This ensures that <acronym>PITR</> servers have all xlog
files needed for recovery.
</para>
</listitem>
<listitem>
<para>
! Add <acronym>WAL</> informational functions (Simon Riggs)
</para>
<para>
--- 489,509 ----
<listitem>
<para>
! Allow a forced switch to a new xlog file (Simon, Tom)
</para>
<para>
! This is valuable for keeping continuous archiving servers
! in sync with the master. xlog file switching also happens
! automatically during <function>pg_stop_backup()</>. This
! ensures that continuous archiving servers have all xlog
files needed for recovery.
</para>
</listitem>
<listitem>
<para>
! Add <acronym>WAL</> informational functions (Simon)
</para>
<para>
***************
*** 517,543 ****
<listitem>
<para>
Allow <acronym>WAL</> replay to be restored quicker in case
! of a crash (Simon Riggs)
</para>
<para>
The server now does periodic checkpoints during <acronym>WAL</>
recovery, so if there is a crash, future <acronym>WAL</>
recovery is shortened. This also eliminates the need for
! <acronym>PITR</> standby servers to replay the entire log
! since the base backup if they crash.
</para>
</listitem>
<listitem>
<para>
Add <varname>archive_timeout</> to force xlog file switches
! at a given interval (Simon Riggs)
</para>
<para>
! This enforces a maximum delay for <acronym>PITR</> standby
! servers.
</para>
</listitem>
--- 517,542 ----
<listitem>
<para>
Allow <acronym>WAL</> replay to be restored quicker in case
! of a crash (Simon)
</para>
<para>
The server now does periodic checkpoints during <acronym>WAL</>
recovery, so if there is a crash, future <acronym>WAL</>
recovery is shortened. This also eliminates the need for
! continuous archive servers to replay the entire log since the
! base backup if they crash.
</para>
</listitem>
<listitem>
<para>
Add <varname>archive_timeout</> to force xlog file switches
! at a given interval (Simon)
</para>
<para>
! This enforces a maximum delay for continuous archive servers.
</para>
</listitem>
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
