Re: Forcing current WAL file to be archived - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Forcing current WAL file to be archived
Date
Msg-id 200607251630.k6PGUro23360@momjian.us
Whole thread Raw
In response to Re: Forcing current WAL file to be archived  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > Assuming such a case, would it be possible to have two functions?
> 
> > pg_stop_backup()
> > pg_stop_backup(boolean); --parameter says log switch or not
> 
> Well, it seems everyone but me thinks that pg_stop_backup should
> force a WAL switch, so I'll yield on that point.  But we still
> need the separate function too, so that people can manually force
> a WAL switch --- just the same as we still have a manual CHECKPOINT
> command.

Agreed, with separate function too.  No sense in limiting the toolkit,
as you explained.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: [PATCHES] Patch for VS.Net 2005's strxfrm() bug
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Loading the PL/pgSQL debugger (and other plugins)