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-06T02:35:03Z
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:
> > > 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.
> 
> We don't have the old cluster after running delete_old_cluster.ch. We use
> pg_dump for backup, so no clogs.  We ended up restored 20 odd dbs totalling
> 2.1TB from the previous days pg_dumps.
> 
> If you review my original report I mentioned that there were only 2 clog
> files in the new cluster both with ctime after the start of postgresql
> after the upgrade. I did the upgrade for three hosts at the same time, the
> others were fine. They have dozens of clogs dating back days before the
> upgrade. The failing system had only 2 recent clog.

That is certainly unusual.

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

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