Horton

Re: [GENERAL] pg_upgrade problem

hubert depesz lubaczewski <depesz@depesz.com>

View thread
From: hubert depesz lubaczewski <depesz@depesz.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Date: 2011-08-25T20:36:41Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. ltree support for multibyte encodings. Patch was made by

On Thu, Aug 25, 2011 at 04:33:07PM -0400, Bruce Momjian wrote:
> The problem appears to be that the Postgres catalogs think there is a
> toast table for 'actions', while the file system doesn't seem to have
> such a file.  I can you look in pg_class and verify that?
> 
> 	SELECT reltoastrelid FROM pg_class WHERE relname  = 'actions';

$ SELECT reltoastrelid FROM pg_class WHERE relname  = 'actions';
 reltoastrelid 
---------------
(0 rows)

This is done not on the pg from backup, but on normal production, as the test
pg instance doesn't work anymore.

I can re-set the test instance, but extracting from backup, and making it apply
all xlogs usually takes 2-3 days.

> > One more thing - one of earlier tests actually worked through
> > pg_upgrade, but when running vacuumdb -az on newly started 9.0.4, I got
> > error about missing transaction/clog - don't remember exactly what it
> > was, though.
> 
> THere was a bug in how how pg_upgrade worked in pre-9.0.4 --- could it
> have been that?

It was done definitely using 9.0.4.

Best regards,

depesz