Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id BD67B133655C for ; Mon, 3 Jan 2011 14:31:32 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 95360-09 for ; Mon, 3 Jan 2011 18:31:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.50]) by mail.postgresql.org (Postfix) with ESMTP id E731E13364DE for ; Mon, 3 Jan 2011 14:31:24 -0400 (AST) Received: (qmail 18708 invoked from network); 3 Jan 2011 18:31:23 -0000 Received: from 25-76-42-72.skybeam.com (HELO [192.168.2.16]) (scott_ribe@killerbytes.com@[72.42.76.25]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 3 Jan 2011 18:31:23 -0000 Subject: Re: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Scott Ribe In-Reply-To: <4D2213EB.7090700@auul.pri.ee> Date: Mon, 3 Jan 2011 11:31:22 -0700 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <42066935-6D27-46E3-8094-836D204816B7@elevated-dev.com> References: <4D2213EB.7090700@auul.pri.ee> To: Imre Oolberg X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201101/13 X-Sequence-Number: 36453 On Jan 3, 2011, at 11:22 AM, Imre Oolberg wrote: > But = http://www.postgresql.org/docs/9.0/interactive/continuous-archiving.html = suggests to use tar on rsync and i guess that PostgreSQL recovery with = wal files takes care of these inconsistencies that are created during = copying filesystem, right? Yes, but the database is recovered to the consistent state as of the = pg_start_backup command, as I pointed out to you before. Results of = transactions that commit after the pg_start_backup command will not be = in the backed up database. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice