From: | Omar Kilani <omar(dot)kilani(at)gmail(dot)com> |
---|---|
To: | Robert Treat <rob(at)xzilla(dot)net> |
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 23:21:20 |
Message-ID: | CA+8F9hgOeet2eAMbAmwwCKQ6phpt1zi+xXzNYYuCiPQE2iu9rg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Robert,
Sounds good. Is it safe to upgrade to 9.2.6 (we're on 9.2.5) in the
mean time, or should we just leave things untouched?
We (unknowingly) got hit by the slave replication bug 2 months ago,
too. That was fun. :)
Omar
On Thu, Dec 5, 2013 at 2:48 PM, Robert Treat <rob(at)xzilla(dot)net> wrote:
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2013-12-05 23:44:12 | Re: Proposal: variant of regclass |
Previous Message | Antonin Houska | 2013-12-05 23:17:59 | Re: Reference to parent query from ANY sublink |