Re: Feature freeze progress report - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Feature freeze progress report
Date
Msg-id 61581.75.177.135.163.1178132644.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: Feature freeze progress report  (Marc Munro <marc@bloodnok.com>)
List pgsql-hackers
Marc Munro wrote:
> On Wed, 2007-02-05 at 08:27 -0400, Andrew Dunstan wrote:
>>
>> Naz Gassiep wrote:
>> > Andrew Dunstan wrote:
>> >
>> >> Naz Gassiep wrote:
>> >>
>> >>> I believe the suggestion was to have an automated process that only
>> ran
>> >>> on known, sane patches.
>> >>>
>> >> How do we know in advance of reviewing them that they are sane?
>> >>
>> > Same way as happens now.
>> >
>>
>> The question was rhetorical ... there is no list of "certified sane but
>> unapplied" patches. You are proceeding on the basis of a faulty
>> understanding of how our processes work.
>
> Why do we need to know the patch is sane?

Because not doing so is dangerous and a major security hole. I won't run
arbitrary code on my machine and I won't create infrastructure (e.g.
buildfarm) to get others to do it either.

You are also conveniently ignoring all the other reasons why this won't
help anyone much (e.g. see Bruce's comments upthread).

cheers

andrew



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Sequential scans
Next
From: Magnus Hagander
Date:
Subject: Optimization in convert_string_datum?