On Thu, Oct 27, 2011 at 6:55 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> It seems cheap to add in a call to LogStandbySnapshot() after each
> call to pg_stop_backup().
> Does anyone think this case is worth adding code for? Seems like one
> more thing to break.
Why at that particular time?
It would maybe nice if the master could notice when it has a plausible
(non-overflowed) snapshot and log it then. But that might be more
code than the problem is worth.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: pasman pasmański||Date: 2011-10-28 04:13:47|
|Subject: Include commit identifier in version() function|
|Previous:||From: Bruce Momjian||Date: 2011-10-28 03:41:01|
|Subject: Re: pg_upgrade if 'postgres' database is dropped|