Re: Forcing WAL switch

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

"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

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Walker, Jed S 2005-08-11 22:14:21 Re: Forcing WAL switch
Previous Message Walker, Jed S 2005-08-11 22:01:46 Re: Forcing WAL switch