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

From Pavel Stehule
Subject Re: Patch: plan invalidation vs stored procedures
Date
Msg-id 162867790808181341r1a0fb37doc8dd8e1e9d260fdf@mail.gmail.com
Whole thread Raw
In response to Re: Patch: plan invalidation vs stored procedures  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: Patch: plan invalidation vs stored procedures  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
2008/8/18 Hannu Krosing <hannu@2ndquadrant.com>:
> On Mon, 2008-08-18 at 11:05 +0200, Pavel Stehule wrote:
>> 2008/8/18 Dimitri Fontaine <dfontaine@hi-media.com>:
>> > Hi,
>> >
>> > Le lundi 18 août 2008, Andrew Dunstan a écrit :
>> >> > On Sat, Aug 16, 2008 at 09:40:19PM -0400, Tom Lane wrote:
>> >> >> This is not the kind of patch we put into stable branches.
>> >>
>> >> So what? That is not the only criterion for backpatching.
>> >
>> > I fail to understand why this problem is not qualified as a bug.
>> >
>>
>> Does it change of result some queries?
>
> Not in the long run, but not invalidating the functions (current
> behaviour) postpones seeing the results of function change until DBA
> manually restarts the error-producing client.
>
>> It is protection to server's hang?
>
> Can't understand this question :(
>
> If you mean, does the change protect against hanging the server, then
> no, currently the server does not actually hang, it just becomes
> unusable until reconnect :(

Hi

I am sorry, but it's really new feature and not bug fix

Pavel
>
> ---------
> Hannu
>
>

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Overhauling GUCS
Next
From: "Asko Oja"
Date:
Subject: Re: Patch: plan invalidation vs stored procedures