Re: Odd behaviour with WAL and pg_stop_backup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Donald Fraser" <postgres(at)kiwi-fraser(dot)net>
Cc: "[ADMIN]" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Odd behaviour with WAL and pg_stop_backup
Date: 2006-09-15 14:17:15
Message-ID: 24298.1158329835@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Donald Fraser" <postgres(at)kiwi-fraser(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2006-09-15 14:25:24 Re: Postgresql 7.4 migration to (partially) new disks
Previous Message Tom Lane 2006-09-15 14:02:30 Re: install postgres8.1 on debian