Re: Forcing WAL switch - Mailing list pgsql-novice

From Walker, Jed S
Subject Re: Forcing WAL switch
Date
Msg-id F7638DABBEBB4A4CB70616DE2B19E6B806729D@COENGEXCMB01.cable.comcast.com
Whole thread Raw
In response to Forcing WAL switch  ("Walker, Jed S" <Jed_Walker@cable.comcast.com>)
Responses Re: Forcing WAL switch  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Forcing WAL switch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
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.

            regards, tom lane

pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: Forcing WAL switch
Next
From: Bruce Momjian
Date:
Subject: Re: Forcing WAL switch