Re: Forcing current WAL file to be archived

Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +