Skip site navigation (1) Skip section navigation (2)

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:22:36
Message-ID: 25963.1123798956@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
"Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com> writes:
>> How is "switch a WAL" an essential component of that scheme?  You can
>> archive the latest active segment just as well.

> How do you do that? 

Look into the backup history file created by pg_stop_backup --- it will
show the starting and ending WAL locations for the backup.  Make sure
you have copies of the WAL segments between those locations inclusive,
and you're done.

The file containing the ending WAL location is probably still active,
and will need to be archived via the normal PITR mechanism when it's
complete (assuming you're doing real PITR archiving), but I don't see
what that has to do with building a standalone backup fileset.

			regards, tom lane

In response to

pgsql-novice by date

Next:From: Tom LaneDate: 2005-08-11 23:11:26
Subject: Re: Forcing WAL switch
Previous:From: Bruce MomjianDate: 2005-08-11 22:20:42
Subject: Re: Forcing WAL switch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group