X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5B7C29FB2A8 for ; Fri, 15 Sep 2006 11:17:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 75842-03 for ; Fri, 15 Sep 2006 11:17:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 096A09FB2A2 for ; Fri, 15 Sep 2006 11:17:23 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8FEHF67024299; Fri, 15 Sep 2006 10:17:15 -0400 (EDT) To: "Donald Fraser" cc: "[ADMIN]" Subject: Re: Odd behaviour with WAL and pg_stop_backup In-reply-to: <000601c6d8c5$161acd50$6464a8c0@DonAcer> References: <000601c6d8c5$161acd50$6464a8c0@DonAcer> Comments: In-reply-to "Donald Fraser" message dated "Fri, 15 Sep 2006 13:47:21 +0100" Date: Fri, 15 Sep 2006 10:17:15 -0400 Message-ID: <24298.1158329835@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.106 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/153 X-Sequence-Number: 23067 "Donald Fraser" 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