Re: Dividing progress/debug information in pg_standby, and stat before copy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id 17092.1264532298@sss.pgh.pa.us
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Dividing progress/debug information in pg_standby, and stat before copy  (Josh Berkus <josh@agliodbs.com>)
Re: Dividing progress/debug information in pg_standby, and stat before copy  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> On 1/26/10 10:48 AM, Heikki Linnakangas wrote:
>> I didn't intend to replace pg_standby when I started this, it just kind
>> of happened. Maybe we should provide a sample script similar to
>> pg_standby, to be used instead of plain 'cp', that does the cleanup too.

> What I'm pointing out is that you haven't *quite* replaced pg_standby,
> and at this late date aren't going to.  Some people will still want to
> use it.  Especially for people who for some reason aren't using SR.

Right, but the question is: is there enough use-case left in it to
justify spending community effort on polishing rough edges?  It's not
like we haven't got plenty else to do to get 9.0 out the door.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: About "Our CLUSTER implementation is pessimal" patch
Next
From: Josh Berkus
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy