Re: txid failed epoch increment, again, aka 6291
| От | Noah Misch |
|---|---|
| Тема | Re: txid failed epoch increment, again, aka 6291 |
| Дата | |
| Msg-id | 20120907124917.GA18507@tornado.leadboat.com обсуждение |
| Ответ на | Re: txid failed epoch increment, again, aka 6291 (Daniel Farina <daniel@heroku.com>) |
| Ответы |
Re: txid failed epoch increment, again, aka 6291
|
| Список | 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@leadboat.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
Вложения
В списке pgsql-hackers по дате отправления: