Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 9C1DE133655C for ; Mon, 3 Jan 2011 14:22:45 -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 93039-10 for ; Mon, 3 Jan 2011 18:22:38 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp1a.aso.ee (smtp1a.aso.ee [213.184.32.86]) by mail.postgresql.org (Postfix) with ESMTP id E272A13364DE for ; Mon, 3 Jan 2011 14:22:37 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1a.aso.ee (Postfix) with ESMTP id 65CF24D8DE for ; Mon, 3 Jan 2011 20:22:35 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at smtp1a.avalik.kit Received: from smtp1a.aso.ee ([127.0.0.1]) by localhost (smtp1a.avalik.kit [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPqMMURJoQaf for ; Mon, 3 Jan 2011 20:22:35 +0200 (EET) Received: from [172.19.10.50] (unknown [172.19.10.50]) by smtp1a.aso.ee (Postfix) with ESMTP id 4491D4D8D6 for ; Mon, 3 Jan 2011 20:22:35 +0200 (EET) Message-ID: <4D2213EB.7090700@auul.pri.ee> Date: Mon, 03 Jan 2011 20:22:35 +0200 From: Imre Oolberg User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Re: pg v. 8.4.5 misses objects and data after restoring from backup using wal References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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/12 X-Sequence-Number: 36452 Hi! Thanks for the answer. On 01/03/11 18:36, pasman pasmański wrote: > The problem exists when you do a base backup with pg_backup? > Maybe rsync skip some data ? > > Yes, problem exists using pg_start/stop_backup as i discribed. I am sure that 'rsync -avH ...' and 'tar cvf ...' will skip at least additions made to the filesystem tree after they are started. In this case rsync says nothing and tar says tar: directory-name: file changed as we read it 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? Imre > ------------ > pasman > >