Re: Problem with pg_upgrade

From: Payal Singh <payals1(at)umbc(dot)edu>
To: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
Subject: Re: Problem with pg_upgrade
Date: 2012-07-06 20:03:38
Message-ID: CAK4ouny5kBCSVtrSFJ1fP6wcSHDPmT_VeSCJ0m-KqOJL1ivZNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The omnipitr-backup-slave process takes online backups from the standby,
and this is done everyday. This process connects to the master and calls a
pg_start_backup and then looks for a restore point on the standby after
that WAL address. So i don't think I need to shut down the server.

Also, it is the omnipitr-backup-slave process that makes a separate backup
for xlog.

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

I'm not sure about that. Didn't try anything else after that. The 9.2beta2
server starts without errors though.

Regards,
Payal

On Fri, Jul 6, 2012 at 3:30 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> 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. +
>

--
Payal Singh
Graduate Student
Department of Computer Science and Electrical Engineering
University of Maryland, Baltimore County

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-07-06 20:05:27 Re: Problem with pg_upgrade
Previous Message Bruce Momjian 2012-07-06 19:30:30 Re: Problem with pg_upgrade