Re: Odd behaviour with WAL and pg_stop_backup - Mailing list pgsql-admin

From Tom Lane
Subject Re: Odd behaviour with WAL and pg_stop_backup
Date
Msg-id 24298.1158329835@sss.pgh.pa.us
Whole thread Raw
In response to Odd behaviour with WAL and pg_stop_backup  ("Donald Fraser" <postgres@kiwi-fraser.net>)
List pgsql-admin
"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

pgsql-admin by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Auto Vacuum not starting unless postgres is restarted
Next
From: Achilleas Mantzios
Date:
Subject: Re: Postgresql 7.4 migration to (partially) new disks