From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Michael Paesold <mpaesold(at)gmx(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rob Butler <crodster2k(at)yahoo(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Jeff Davis <jdavis-pgsql(at)empires(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Problem with PITR recovery |
Date: | 2005-04-21 20:29:53 |
Message-ID: | 1114115393.16721.2345.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2005-04-21 at 08:57 -0400, Bruce Momjian wrote:
> Michael Paesold wrote:
> > Tom Lane wrote:
> > > Bruce Momjian wrote:
> > >> OK, makes sense. Could we give them a command to archive it before they
> > >> shut down? That would make sense.
> > >
> > > Not if the idea is to be certain you got everything ... I think what we
> > > have to do is document a manual procedure for archiving the last XLOG
> > > file.
> >
> > What Bruce would want is a way to "stop new transactions, archive and
> > shutdown", which would do this atomically. Then we could have another
> > shutdown switch for pg_ctl.
>
> Yea, probably a separate switch, or an additional switch to pg_clt would
> be best, but then we have to add to pg_ctl.
>
> > But yea, a documentation for a manual procedure would be ok, too, just not
> > as user friendly.
>
> Right. I just hate the 'do this, do that' instructions to PITR. When
> they get too long/complex, I get worried.
> I am thinking a special pg_ctl flag, and disabling -W for that so you
> have to wait for the success message. Of course we then have to
> document the use of the pg_ctl flag then.
I'll write the log switch, you decide when/how to invoke it.
My head hurts.
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-04-21 22:20:05 | Re: Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords |
Previous Message | Lance James | 2005-04-21 19:48:04 | Re: Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords |