Re: Standbys, txid_current_snapshot, wraparound

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Daniel Farina <daniel(at)heroku(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Standbys, txid_current_snapshot, wraparound
Date: 2012-03-23 08:52:40
Message-ID: CA+U5nMLo9wGwDGxTUwsB7D0Cy4evPYLRaLGHibW+UhVcKT2FnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 23, 2012 at 12:26 AM, Daniel Farina <daniel(at)heroku(dot)com> wrote:

> Some time ago I reported bug 6291[0], which reported a Xid wraparound,
> both as reported in pg_controldata and by txid_current_snapshot.
> Unfortunately, nobody could reproduce it.
>
> Today, the same system of ours just passed the wraparound mark
> successfully at this time, incrementing the epoch.  However, two
> standbys have not done the same: they have wrapped to a low txid.  At
> this time, pg_controldata does report the correct epoch, as I read it,
> unlike the original case.
>
> I have not yet tried to reproduce this in a minimal way, but I wanted
> to relate this information as soon as possible.
>
> These systems are 9.0.6, on Ubuntu 10.04 LTS, amd64.
>
> [0]: http://archives.postgresql.org/pgsql-bugs/2011-11/msg00094.php

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?

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2012-03-23 08:56:18 Re: Reporting WAL file containing checkpoint's REDO record in pg_controldata's result
Previous Message Jaime Casanova 2012-03-23 05:06:56 Re: Reporting WAL file containing checkpoint's REDO record in pg_controldata's result