Re: [HACKERS]odd output in restore mode
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
- Cc: "Martin Zaun" <Martin(dot)Zaun(at)Sun(dot)COM>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Dave Page" <dpage(at)pgadmin(dot)org>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "List pgsql-patches" <pgsql-patches(at)postgresql(dot)org>
- Subject: Re: [HACKERS]odd output in restore mode
- Date: Thu, 31 Jul 2008 12:32:38 -0400
- Message-id: <9981.1217521958@sss.pgh.pa.us> <text/plain>
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
> Martin Zaun wrote:
>> With these avenues to be explored, can the pg_standby patch on the
>> CommitFest wiki be moved to the "Returned with Feedback" section?
> Yes, I think we can conclude that we don't want this patch as it is.
> Instead, we want a documentation patch that describes the problem,
> mentioning that GNU cp is safe, or you can use the copy+rename trick.
Right, after which we remove the presently hacked-in delay.
I've updated the commitfest page accordingly.
regards, tom lane
Home |
Main Index |
Thread Index