Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] 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: [PATCHES] odd output in restore mode
Date: 2008-07-31 16:32:38
Message-ID: 9981.1217521958@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"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

In response to

Responses

pgsql-hackers by date

Next:From: David FetterDate: 2008-07-31 16:34:19
Subject: Re: window function v03 against HEAD
Previous:From: Heikki LinnakangasDate: 2008-07-31 16:05:16
Subject: Re: [PATCHES] odd output in restore mode

pgsql-patches by date

Next:From: Heikki LinnakangasDate: 2008-08-01 11:26:53
Subject: Re: Relation forks & FSM rewrite patches
Previous:From: Heikki LinnakangasDate: 2008-07-31 16:05:16
Subject: Re: [PATCHES] odd output in restore mode

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group