Re: Streaming Replication docs

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
>
>    ...
>    21. Managing Databases
>    22. Localization
>    23. Routine Database Maintenance Tasks
>    24. Backup and Restore
>    25. High Availability, Load Balancing, and Replication
> *    26. Recovery Configuration *
>    27. Monitoring Database Activity
>    28. Monitoring Disk Usage
>    29. Reliability and the Write-Ahead Log
>    30. Regression Tests
>
> Thoughts, better ideas?

+1

> Another change I'd like to make is to document the new built-in way (ie.
> standby_mode='on', restore_command='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='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,

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