Re: Patch: plan invalidation vs stored procedures - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Patch: plan invalidation vs stored procedures
Date
Msg-id 48A8F02C.8090208@dunslane.net
Whole thread Raw
In response to Re: Patch: plan invalidation vs stored procedures  (David Fetter <david@fetter.org>)
Responses Re: Patch: plan invalidation vs stored procedures  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers

David Fetter wrote:
> On Sat, Aug 16, 2008 at 09:40:19PM -0400, Tom Lane wrote:
>   
>> "Asko Oja" <ascoja@gmail.com> writes:
>>     
>>> Is it possible to get it into some official 8.3.x release
>>>       
>> This is not the kind of patch we put into stable branches.
>>     
>
> Does this really count as a user-visible change, except in the sense
> that they won't see things erroring out?  It doesn't add new syntax,
> as far as I can tell.
>
>   

So what? That is not the only criterion for backpatching.

The bigger the change the more resistance there will be to backpatching 
it. Code stability is a major concern.

cheers

andrew


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Overhauling GUCS
Next
From: leiyonghua
Date:
Subject: Re: about postgres-r setup.