On Fri, Aug 21, 2009 at 5:03 PM, Greg Stark<gsst...@mit.edu> wrote: > On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski<ra...@pld-linux.org> > wrote: > > Here's a dump of that page btw. ... [crap word-wrapped by gmail]
Sorry, clearly gmail sucks for posting things that you actually care about how they're formatted. I've attached the page dump. It looks like the row *was* updated by transaction 6179 and the new version was stored in line pointer 12. However it's marked XMAX_INVALID which means at least somebody at some point thought 6179 had aborted and marked that hint bit. Do we have any tools to look up a transaction id status in the clog? Or alternatively do you have all the wal logs and could you run xlogdump on them looking for transaction id 6179? -- greg http://mit.edu/~gsstark/resume.pdf
promocje.page
Description: Binary data
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
