Postgres Pro
Downloads
Home   >   mailing lists

Re: Hot Standby startup with overflowed snapshots - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hot Standby startup with overflowed snapshots
Date
Msg-id CA+TgmoZpxRxrPWxp6c1jScxG66tEBKXxUuLxSRxUV3Oao-xyqQ@mail.gmail.com
Whole thread Raw
In response to Re: Hot Standby startup with overflowed snapshots  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view 
On Thu, Oct 27, 2011 at 6:55 PM, Simon Riggs <simon@2ndquadrant.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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade if 'postgres' database is dropped
Next
From: pasman pasmański
Date:
Subject: Include commit identifier in version() function