Re: Large C files - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Large C files
Date
Msg-id CA+U5nMLEp1A1A7h3gJ4=AfTYmHPSbJ3a3+RrXqcOH8bBvSqj4Q@mail.gmail.com
Whole thread Raw
In response to Re: Large C files  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Large C files
List pgsql-hackers
On Wed, Sep 7, 2011 at 9:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> Please lets not waste effort on refactoring efforts in mid dev cycle.
>
> Say what?  When else would you have us do it?

When else would you have us develop?

Major changes happen at start of a dev cycle, after some discussion.
Not in the middle and especially not for low priority items. It's not
even a bug, just code beautification.

We've all accepted the need for some change, but I would like to see
it happen slowly and carefully because of the very high risk of
introducing bugs into stable code that doesn't have a formal
verification mechanism currently. Anybody that could be trusted to
make those changes ought to have something better to do. If they don't
then that is in itself a much more serious issue than this.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: postgresql.conf archive_command example
Next
From: Simon Riggs
Date:
Subject: Re: postgresql.conf archive_command example