From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | daveg <daveg(at)sonic(dot)net> |
Cc: | hubert depesz lubaczewski <depesz(at)depesz(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] pg_upgrade problem |
Date: | 2011-09-06 02:35:03 |
Message-ID: | 201109060235.p862Z3w25939@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Venkat Balaji | 2011-09-06 05:50:34 | Re: warm standby - apply wal archives |
Previous Message | daveg | 2011-09-06 02:17:28 | Re: [GENERAL] pg_upgrade problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-09-06 02:48:42 | Re: regular logging of checkpoint progress |
Previous Message | Robert Haas | 2011-09-06 02:32:56 | Re: savepoint commit performance |