| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Standbys, txid_current_snapshot, wraparound |
| Date: | 2012-03-23 17:38:31 |
| Message-ID: | CAAZKuFYGt4yDe97e2hNNCFjXW44Dnq+i7w6JfGhyBVB7KJ3iQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 23, 2012 at 1:52 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> So we have this?
>
> Master pg_controldata - OK txid_current_snapshot() - OK
> Standby pg_controldata - OK txid_current_snapshot() - lower value
>
> Are there just 2 standbys? So all standbys have acted identically?
Yes, I believe this is the situation. All have acted identically.
Also, some new data:
I took a new base backup after the epoch increment and started a new
standby, and it reported txid_current_snapshot correctly, at least
moments after it became consistent. This morning, however, it does
not, and reports the 0-epoch number.
--
fdr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2012-03-23 17:51:12 | Re: query cache |
| Previous Message | Fujii Masao | 2012-03-23 17:05:59 | Re: Reporting WAL file containing checkpoint's REDO record in pg_controldata's result |