DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=uBT/V0TXjDb+/X28pVMKFY+XA1GotDfkNTfaMymF7N1l2qmUZsrVy0jJ6GULOidfgg
	psBGflVB1+cmbFIAgBQnQpv+TSE3JcLBulPR0ucciZbCmdH3PTlrVsOK4K3UIAk5RGy9
	mNrJ2GwzruluGCdpm9njsOJPxOO2U5WLIog30=
MIME-Version: 1.0
In-Reply-To: <4B751BEA.7000202@enterprisedb.com>
References: <4B751BEA.7000202@enterprisedb.com>
Date: Fri, 12 Feb 2010 19:09:40 +0900
Message-ID: <3f0b79eb1002120209i3afd935exd2e875ac11df19d7@mail.gmail.com>
Subject: Re: Streaming Replication docs
From: Fujii Masao <masao.fujii@gmail.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 12, 2010 at 6:14 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> So the new layout would be:
>
> III. Server Administration
>
> =A0 =A0...
> =A0 =A021. Managing Databases
> =A0 =A022. Localization
> =A0 =A023. Routine Database Maintenance Tasks
> =A0 =A024. Backup and Restore
> =A0 =A025. High Availability, Load Balancing, and Replication
> * =A0 =A026. Recovery Configuration *
> =A0 =A027. Monitoring Database Activity
> =A0 =A028. Monitoring Disk Usage
> =A0 =A029. Reliability and the Write-Ahead Log
> =A0 =A030. Regression Tests
>
> Thoughts, better ideas?

+1

> Another change I'd like to make is to document the new built-in way (ie.
> standby_mode=3D'on', restore_command=3D'cp ...', primary_conninfo not set=
)
> as the primary way of implementing file-based log shipping. Using
> pg_standby or similar scripts that do the waiting would still be
> documented, but I'd like to de-emphasize it, moving it into an
> "Alternative way to implement File-based log shipping" section. The
> description would go along the lines of "An alternative way to implement
> File-based log shipping is to leave standby_mode=3D'false', and use a
> restore_command that waits until the next WAL file arrives. This offers
> more flexibility and control over the process. ..."

+1

We might need to add the following code of pg_standby into the core,
to prefer it for many cases.

> #ifdef WIN32
>
> 			/*
> 			 * Windows 'cp' sets the final file size before the copy is
> 			 * complete, and not yet ready to be opened by pg_standby. So we
> 			 * wait for sleeptime secs before attempting to restore. If that
> 			 * is not enough, we will rely on the retry/holdoff mechanism.
> 			 * GNUWin32's cp does not have this problem.
> 			 */
> 			pg_usleep(sleeptime * 1000000L);
> #endif

Regards,

--=20
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center