Re: txid failed epoch increment, again, aka 6291

From: Noah Misch <noah(at)leadboat(dot)com>
To: Daniel Farina <daniel(at)heroku(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: txid failed epoch increment, again, aka 6291
Date: 2012-09-07 12:49:17
Message-ID: 20120907124917.GA18507@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 07, 2012 at 01:37:57AM -0700, Daniel Farina wrote:
> On Thu, Sep 6, 2012 at 3:04 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
> > On Tue, Sep 04, 2012 at 09:46:58AM -0700, Daniel Farina wrote:
> >> I might try to find the segments leading up to the overflow point and
> >> try xlogdumping them to see what we can see.
> >
> > That would be helpful to see.
> >
> > Just to grasp at yet-flimsier straws, could you post (URL preferred, else
> > private mail) the output of "objdump -dS" on your "postgres" executable?
>
> https://dl.dropbox.com/s/444ktxbrimaguxu/txid-wrap-objdump-dS-postgres.txt.gz

Thanks. Nothing looks amiss there.

I've attached the test harness I used to try reproducing this. It worked
through over 500 epoch increments without a hitch; clearly, it fails to
reproduce an essential aspect of your system. Could you attempt to modify it
in the direction of better-resembling your production workload until it
reproduces the problem?

nm

Attachment Content-Type Size
burnxid.shar application/x-shar 11.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit kapila 2012-09-07 13:14:56 Re: [WIP PATCH] for Performance Improvement in Buffer Management
Previous Message Kevin Grittner 2012-09-07 12:36:33 Re: pg_dump transaction's read-only mode