Bruce Momjian wrote:
> > After a quick chat with Bruce it was determined that we don't freeze
> > anything (it would be horrid for downtime if we did so in pg_migrator;
> > and it would be useless if ran anywhere else). What we do is migrate
> > pg_clog from the old cluster to the new. So never mind that hypothesis.
> > Bruce noticed that the pg_dump/pg_migrator combo is failing to restore
> > pg_largeobject's relfrozenxid. We're not sure how this is causing the
> > errors Jamie is seeing, because what I think should happen is that scans
> > of the table should fail with failures to open pg_clog files
> > such-and-such, but not missing tuples ...
> Jamie, is it possible for you to apply the attached patch to the 8.4
> server, install the new pg_dump, and run the test again to see if
> pg_largeobject is fixed? This patch properly sets the relfrozenxid in
> the system tables for each database.
I have applied the attached patch to have pg_dump restore
pg_largeobject.relfrozenxid in binary upgrade mode; backpatched to
This doesn't fix the reported problem, but it is still a bug.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
Description: text/x-diff (2.4 KB)
In response to
pgsql-hackers by date
|Next:||From: Greg Stark||Date: 2009-07-20 21:21:29|
|Subject: Re: [PATCH v4] Avoid manual shift-and-test logic in AllocSetFreeIndex|
|Previous:||From: Alvaro Herrera||Date: 2009-07-20 20:50:00|
|Subject: Re: fmgroids.h not installed by "make install" in VPATH|
pgsql-general by date
|Next:||From: Bruce Momjian||Date: 2009-07-20 22:06:57|
|Subject: Re: [GENERAL] large object does not exist after
|Previous:||From: CG||Date: 2009-07-20 19:09:07|
|Subject: Re: best practice transitioning from one datatype to another|