Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0E18364FD91 for ; Wed, 15 Oct 2008 11:59:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 55789-10 for ; Wed, 15 Oct 2008 11:58:48 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by postgresql.org (Postfix) with ESMTP id 36F2064FD82 for ; Wed, 15 Oct 2008 11:58:48 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so2474443rvf.43 for ; Wed, 15 Oct 2008 07:58:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=mccgV4ltdNOL4oQYic+qU69UrSPIygzo18psfAB4HA4=; b=s67b/8olwLKIxHB6AB55w4fSlC3b5QVTFcxT+WKtR4G17jBYi3gZyOn3eJTVALUcCD +odR0+uvTdwYgfnrxoIpN7/aqEaoYL/XGNs1ifsEf/Xgtw4e9I7KJN0b/IsmAZXUPidx STlF34IYsTTmY6EKlnfGIn9ucc0XPOfVywwyM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=FvJjcNvivb8Lptiprt7OYuXsLwjyLdL5QTw2HjBaAL0XP0S4i0UVEruhY2ilEu76km JbW8bfhkmOHvgTY/UQx8nlBX2f2Dt+wjyyakaS07YcG9drbHbSXzkMlL5hkq1kvUcVQh AnzK3a+BAOn1OEloutkKL1v4q1g4CPLrFM62s= Received: by 10.141.116.17 with SMTP id t17mr677550rvm.251.1224082726629; Wed, 15 Oct 2008 07:58:46 -0700 (PDT) Received: by 10.141.153.13 with HTTP; Wed, 15 Oct 2008 07:58:46 -0700 (PDT) Message-ID: <9bbcef730810150758i4cc25431g41e4805c024615fd@mail.gmail.com> Date: Wed, 15 Oct 2008 16:58:46 +0200 From: "Ivan Voras" To: "Aidan Van Dyk" Subject: Re: Backup strategies Cc: pgsql-performance@postgresql.org In-Reply-To: <20081015141327.GW16893@yugib.highrise.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48F4D693.9000304@lerner.co.il> <48F5BBFC.80404@krogh.cc> <48F5D6AE.3000601@lelarge.info> <20081015141327.GW16893@yugib.highrise.ca> X-Google-Sender-Auth: da9f1adfe532bdd2 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/87 X-Sequence-Number: 31668 2008/10/15 Aidan Van Dyk : > * Ivan Voras [081015 10:05]: > >> So, pg_start_backup() freezes the data at the time it's called but still >> data and xlog are changed, in a different way that's safe to backup? Why >> not run with pg_start_backup() always enabled? > > I think your missing the whole point of "pg_start_backup()". > pg_start_backup()" is *part* of a full PITR/backup run. i.e. you use it > when you have an archive command working as well. It's *not* mean tto > just allow you to do a filesystem copy inside a running data directory. Possibly - that's why I'm sticking to this thread :) My context is doing full filesystem-only copies/backups of the database (xlogs & all) - is pg_start_backup() applicable?