Re: Forcing WAL switch - Mailing list pgsql-novice

From Bruce Momjian
Subject Re: Forcing WAL switch
Date
Msg-id 200508112220.j7BMKgX15759@candle.pha.pa.us
Whole thread Raw
In response to Re: Forcing WAL switch  ("Walker, Jed S" <Jed_Walker@cable.comcast.com>)
Responses Re: Forcing WAL switch
List pgsql-novice
Walker, Jed S wrote:
> How do you do that?
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Thursday, August 11, 2005 4:12 PM
> To: Walker, Jed S
> Cc: pgsql-novice@postgresql.org
> Subject: Re: [NOVICE] Forcing WAL switch
>
> "Walker, Jed S" <Jed_Walker@cable.comcast.com> writes:
> > If the backup completes, I switch the database out of "backup mode",
> > and then switch a WAL and it archives, then I know my backup directory
>
> > contains the backup and the WAL(s) needed to bring the database to a
> > consistent state. So, if I can switch a WAL after the backup, then I
> > truly have a complete backup.
>
> How is "switch a WAL" an essential component of that scheme?  You can
> archive the latest active segment just as well.

Ah, but that will be over-written later, so you have to store it
somewhere safe, rather than just forcing closure of the current
WAL file and forcing an archive of it.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-novice by date:

Previous
From: "Walker, Jed S"
Date:
Subject: Re: Forcing WAL switch
Next
From: Tom Lane
Date:
Subject: Re: Forcing WAL switch