On 03/07/10 18:32, Tom Lane wrote:
> Heikki Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> It would seem logical to use the same logic for archive recovery as we
>> do for streaming replication, and only set XLogReceiptTime when you have
>> to wait for a WAL segment to arrive into the archive, ie. when
>> restore_command fails.
> That would not do what you want at all in the case where you're
> recovering from archive --- XLogReceiptTime would never advance
> at all for the duration of the recovery.
Do you mean when using something like pg_standby, which does the waiting
> It might be useful if you knew that it was a standby-with-log-shipping
> situation, but we have no way to tell the difference.
With pg_standby etc. you use standby_mode=off. Same with traditional
archive recovery. In standby mode, it's on.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-07-03 19:34:37|
|Subject: Re: Keeping separate WAL segments for each database|
|Previous:||From: Simon Riggs||Date: 2010-07-03 18:03:05|
|Subject: Re: Why is vacuum_defer_cleanup_age PGC_USERSET?|