Postgres Pro
Downloads
Home   >   mailing lists

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

From Donald Fraser
Subject Odd behaviour with WAL and pg_stop_backup
Date
Msg-id 000601c6d8c5$161acd50$6464a8c0@DonAcer
Whole thread Raw
Responses Re: Odd behaviour with WAL and pg_stop_backup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tree view 
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

pgsql-admin by date:

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