Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 45EDE6501CA;
	Fri, 25 Jul 2008 17:31:52 -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 97181-04; Fri, 25 Jul 2008 17:31:45 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 67B1D650058;
	Fri, 25 Jul 2008 17:31:48 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m6PKVQ5a000399;
	Fri, 25 Jul 2008 16:31:26 -0400 (EDT)
To: Simon Riggs <simon@2ndquadrant.com>
cc: Martin Zaun <Martin.Zaun@Sun.COM>, Bruce Momjian <bruce@momjian.us>,
	Heikki Linnakangas <heikki@enterprisedb.com>,
	Andrew Dunstan <andrew@dunslane.net>, Dave Page <dpage@pgadmin.org>,
	List pgsql-patches <pgsql-patches@postgresql.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [PATCHES] odd output in restore mode 
In-reply-to: <1217015178.3894.992.camel@ebony.2ndQuadrant> 
References: <200807011520.m61FKhZ20311@momjian.us> <48867904.9090001@sun.com>
	<1217015178.3894.992.camel@ebony.2ndQuadrant>
Comments: In-reply-to Simon Riggs <simon@2ndquadrant.com>
	message dated "Fri, 25 Jul 2008 20:46:18 +0100"
Date: Fri, 25 Jul 2008 16:31:26 -0400
Message-ID: <398.1217017886@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
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: 200807/1217
X-Sequence-Number: 121477

Simon Riggs <simon@2ndquadrant.com> writes:
> On Tue, 2008-07-22 at 17:19 -0700, Martin Zaun wrote:
>> reviewing your patch 

> Current status is this:
> * My understanding is that Dave and Andrew (and therefore Simon) think
> the approach proposed here is an acceptable one. Heikki disagrees and
> wants different approach. Perhaps I misunderstand.
> * Patch needs work to complete the proposed approach
> * I'm willing to change the patch, but not able to test it on Windows.

I thought the latest conclusion was that changing the behavior of
pg_standby itself wouldn't address the problem anyway, and that what we
need is just a docs patch recommending that people use safe copying
methods in their scripts that copy to the archive area?

			regards, tom lane