| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Chris Redekop <chris(at)replicon(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot Standby startup with overflowed snapshots |
| Date: | 2011-10-28 03:42:20 |
| Message-ID: | CA+TgmoZpxRxrPWxp6c1jScxG66tEBKXxUuLxSRxUV3Oao-xyqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pasman pasmański | 2011-10-28 04:13:47 | Include commit identifier in version() function |
| Previous Message | Bruce Momjian | 2011-10-28 03:41:01 | Re: pg_upgrade if 'postgres' database is dropped |