Thread: Odd behaviour with WAL and pg_stop_backup

PostgreSQL 8.0.7
OS: Linux Red Hat 4.0


We have been testing the on-line backup of PostgreSQL and after issuing a
pg_stop_backup() PostgreSQL is still using the archive command, as set in
postgresql.conf, for every new WAL block generated.

It appears the only way to truly stop it from using the archive command is to
edit the postgresql.conf file, remove the archive command and either issue a
SIGHUP or a server restart.

Can someone confirm that this is the correct behaviour or not?

Thanks in advance,
Donald Fraser

"Donald Fraser" <postgres@kiwi-fraser.net> writes:
> We have been testing the on-line backup of PostgreSQL and after issuing a
> pg_stop_backup() PostgreSQL is still using the archive command, as set in
> postgresql.conf, for every new WAL block generated.

Um ... why would that surprise you?  That facility is designed for
continuous archiving of WAL.  If you want to make a one-shot dump,
pg_dump is a much better tool.

            regards, tom lane