Re: Forcing WAL switch

From: "Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Forcing WAL switch
Date: 2005-08-11 22:14:21
Message-ID: F7638DABBEBB4A4CB70616DE2B19E6B806729D@COENGEXCMB01.cable.comcast.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

How do you do that?

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, August 11, 2005 4:12 PM
To: Walker, Jed S
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Forcing WAL switch

"Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)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

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Bruce Momjian 2005-08-11 22:20:42 Re: Forcing WAL switch
Previous Message Tom Lane 2005-08-11 22:11:30 Re: Forcing WAL switch