Horton

Re: [GENERAL] pg_upgrade problem

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: daveg <daveg@sonic.net>
Cc: hubert depesz lubaczewski <depesz@depesz.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-09-06T00:19:21Z
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

daveg wrote:
> > Can you tell me what table is showing this error?  Does it happen during
> > vacuum?  Can you run a vacuum verbose to see what it is throwing the
> > error on?  Thanks.
> 
> This was upgrading from 8.4.8 to 9.0.4. I don't have the running cluster
> anymore, but I do have tar.gz archives of it and could probably find
> 2TB free somewhere to restore it to if there is something useful to extract.
> 
> However, I don't think this was toast related. Most of our rows are short and 
> have only int, float, and short text columns. These errors hit over 60
> different tables mostly during the analyzes we ran immediately after the
> upgrade. It also hit during select, insert and delete statements. We did not
> run the db more than a few minutes as the damage was so extensive.
> 
> As far as I can tell pg_upgrade never copied any pg_clog files from the
> old cluster to the new cluster. I wish I had detected that before running
> the remove_old_cluster.sh script.

Wow, no clogs?  That would make the system very confused.  You can pull
the clogs out of the old backup and move them over if the files don't
already exist.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +