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 17:42:28
Message-ID: F7638DABBEBB4A4CB70616DE2B19E6B8067279@COENGEXCMB01.cable.comcast.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

To have a good hot backup. It is worthless if I don't have the log that
was being written to at the time the backup was occurring correct? If
I'm wrong please explain.

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, August 11, 2005 9:04 AM
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:
> I can't find a way to force a WAL to switch other than just generating

> a lot of changes in the database. I'd like to be able to switch to the

> next WAL before a hot backup, and then switch out one after the hot
> backup.

What's the point?

regards, tom lane

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message operationsengineer1 2005-08-11 18:50:02 Cast Problem
Previous Message Tim Goodaire 2005-08-11 16:30:52 Re: loading data for newb