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

From Tom Lane
Subject Re: Forcing current WAL file to be archived
Date
Msg-id 17587.1153844987@sss.pgh.pa.us
Whole thread Raw
In response to Re: Forcing current WAL file to be archived  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Forcing current WAL file to be archived  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Forcing current WAL file to be archived
Next
From: "Hiroshi Saito"
Date:
Subject: Re: [PATCHES] Patch for VS.Net 2005's strxfrm() bug