On Fri, Aug 26, 2011 at 05:28:35PM +0200, hubert depesz lubaczewski wrote:
> On Fri, Aug 26, 2011 at 12:18:55AM -0400, Bruce Momjian wrote:
> > OK, this was very helpful. I found out that there is a bug in current
> > 9.0.X, 9.1.X, and HEAD that I introduced recently when I excluded temp
> > tables. (The bug is not in any released version of pg_upgrade.) The
> > attached, applied patches should fix it for you. I assume you are
> > running 9.0.X, and not 9.0.4.
> pg_upgrade worked. Now I'm doing reindex and later on vacuumdb -az.
vacuumdb failed. The fail looks very similar to the one I had on 9.0.4.
After long vacuum I got:
INFO: vacuuming "pg_toast.pg_toast_106668498"
vacuumdb: vacuuming of database "etsy_v2" failed: ERROR: could not access status of transaction 3429738606
DETAIL: Could not open file "pg_clog/0CC6": No such file or directory.
Unfortunately at the moment, I no longer have the old (8.3) setup, but I do
have the 9.0.X and will be happy to provide any info you might need to help me
debug/fix the problem.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2011-08-29 16:58:19|
|Subject: Re: limit in subquery causes poor selectivity estimation|
|Previous:||From: Robert Haas||Date: 2011-08-29 16:53:51|
|Subject: Re: spinlocks on HP-UX|
pgsql-general by date
|Next:||From: hubert depesz lubaczewski||Date: 2011-08-29 17:49:24|
|Subject: Re: [GENERAL] pg_upgrade problem|
|Previous:||From: Martín Marqués||Date: 2011-08-29 16:48:48|
|Subject: Re: passing cursors from one PL function to another|