Re: How to detect invisible rows caused by the relfrozenxid bug?

From: Robert Treat <rob(at)xzilla(dot)net>
To: Omar Kilani <omar(dot)kilani(at)gmail(dot)com>
Cc: postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: How to detect invisible rows caused by the relfrozenxid bug?
Date: 2013-12-05 22:48:21
Message-ID: CABV9wwNXXYVZ-c_aNrsYQeuuJB=yBfF3MjNTeZeqEQyXR=uC6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 5, 2013 at 4:14 PM, Omar Kilani <omar(dot)kilani(at)gmail(dot)com> wrote:
> Hi,
>
> How would one go about detecting whether they've lost rows due to the
> relfrozenxid?
>
> Unfortunately running 'SELECT txid_current() < 2^31' on our DB returns
> false, and I'm a little bit worried, since we've been seeing some
> WeirdStuff(tm) lately.
>
> We're "only" 200M txids or so past 2^31.
>

We've been working on coming up with a way to determine this, and I
think we're pretty close, so if you can hang tight for a bit,
hopefully we can post something.

That said, if anyone else has come up with a method, I'd be interested
in looking at it.

Robert Treat
play: xzilla.net
work: omniti.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-12-05 23:15:42 Re: pg_archivecleanup bug
Previous Message Michael Paquier 2013-12-05 21:50:18 Re: Regression tests failing if not launched on db "regression"