Re: Problem with pg_upgrade

On Fri, Jul 06, 2012 at 02:22:28PM -0400, Payal Singh wrote:
> The first message in the log is probably because the backup is taken from a
> standby. I am using omnipitr-backup-slave to make the backups and then
> restoring one of those.

OK, this is what I wanted to see. Is the server running while you are
taking these backups, because that will not work.

> The whole process that I followed is:
>
>
> 1. Restoring backup file:
> 2.
> 3. payal(at)sparedb1:/data/pg$ sudo tar -xvzf /mnt/nas/backups/postgres/
> userslave2/backups/data/userslave2.int.functionx.net-xlog-2012-07-03.tar.gz

> 489. payal(at)sparedb1:/data/pg$ sudo tar -xvzf /mnt/nas/backups/postgres/
> userslave2/backups/data/userslave2.int.functionx.net-xlog-2012-07-03.tar.gz
> 490. 9.1/pg_xlog/
> 491. 9.1/pg_xlog/000000010000027C00000070
> 492. 9.1/pg_xlog/000000010000027C0000006B.009707C0.backup
> 493. 9.1/pg_xlog/000000010000027C0000006D
> 494. 9.1/pg_xlog/000000010000027C0000006C
> 495. 9.1/pg_xlog/000000010000027C0000006B
> 496. 9.1/pg_xlog/000000010000027C0000006E
> 497. 9.1/pg_xlog/000000010000027C00000071
> 498. 9.1/pg_xlog/000000010000027C0000006F

Why is the xlog backup a separate step? Because it is a separate file
system? The system is down, I assume.

If you run vacuumedb now, does everything later work fine?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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