"Tom Lane" <[EMAIL PROTECTED]> writes: > Whether it's a good idea or not is a bit debatable though. I'm > concerned about the WAL partition filling up (--> PANIC), especially > if you forget to pg_stop_backup after getting your backup.
We check if pg_start_backup in effect when we an ENOSPC error on the WAL partition and if so turn it off, clean old WAL segments, and march on. The major concern being that someone might have a bad backup. pg_stop_backup() could scream but they might not notice. Not sure how much more we could do about that. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
