Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id E87A96327C9 for ; Thu, 11 Feb 2010 15:50:32 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 14368-10 for ; Thu, 11 Feb 2010 19:50:10 +0000 (UTC) X-Greylist: delayed 00:05:05.367641 by SQLgrey-1.7.6 Received: from smtp2.exchange.upenn.edu (smtp2.exchange.upenn.edu [128.91.3.225]) by mail.postgresql.org (Postfix) with ESMTP id 3CB9263014E for ; Thu, 11 Feb 2010 15:50:22 -0400 (AST) Received: from isc.upenn.edu (128.91.197.64) by smtp.exchange.upenn.edu (128.91.2.25) with Microsoft SMTP Server (TLS) id 8.2.213.0; Thu, 11 Feb 2010 14:45:14 -0500 Date: Thu, 11 Feb 2010 14:45:13 -0500 From: Garick Hamlin To: Kevin Grittner CC: Heikki Linnakangas , Aidan Van Dyk , Simon Riggs , Fujii Masao , PostgreSQL-development Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL Message-ID: <20100211194513.GC5500@isc.upenn.edu> References: <4B73FB99.4080403@enterprisedb.com> <1265893599.7341.1454.camel@ebony> <4B740613.5090004@enterprisedb.com> <20100211140118.GB14128@oak.highrise.ca> <4B74118C.30704@enterprisedb.com> <20100211144204.GC14128@oak.highrise.ca> <4B7438A9.8090902@enterprisedb.com> <20100211173154.GD14128@oak.highrise.ca> <4B74485A.3050804@enterprisedb.com> <4B73F694020000250002F1E0@gw.wicourts.gov> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <4B73F694020000250002F1E0@gw.wicourts.gov> User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.293 tagged_above=-10 required=5 tests=AWL=2.306, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/931 X-Sequence-Number: 157274 On Thu, Feb 11, 2010 at 01:22:44PM -0500, Kevin Grittner wrote: > Heikki Linnakangas wrote: > > > I think 'rsync' has the same problem. > > There is a switch you can use to create the problem under rsync, but > by default rsync copies to a temporary file name and moves the > completed file to the target name. > > -Kevin I don't use PITR, So I don't know any of the well understood facts about PITR with postgres, but my understanding with rsync is ... It doesn't fsync data before rename, its something like: open / write / close / rename, which could lead to zero length files on some filesystems. (are there other anomalies to worry about here?) Would that be a concern? Garick > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers