Re: plan invalidation vs stored procedures

From: "Asko Oja" <ascoja(at)gmail(dot)com>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "Marko Kreen" <markokr(at)gmail(dot)com>, "Martin Pihlak" <martin(dot)pihlak(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plan invalidation vs stored procedures
Date: 2008-08-06 18:35:22
Message-ID: ecd779860808061135y4894cf7fl4397c174e79a4184@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Don't you think we try to be careful but still we manage to overlook several
times in year something and cause some stupid downtime.

On Wed, Aug 6, 2008 at 9:13 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:

> On Wed, Aug 6, 2008 at 2:20 AM, Marko Kreen <markokr(at)gmail(dot)com> wrote:
> > But the main problem is that if the DROP/CREATE happens, the failure
> > mode is very nasty - you get permanent error on existing backends.
> > (Main case I'm talking about is functions calling other functions.)
> >
> > Some sorta recovery mode would be nice to have, it does not even
> > need function perfectly. Giving error once and then recover would
> > be better than requiring manual action from admin.
>
> sure -- this a known issue --, but the point is that there are not
> that many reasons why you have to drop/create a function if you are
> careful. hiding function prototypes is actually pretty powerful
> although you have to deal with creating the extra types.
>
> merlin
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2008-08-06 18:42:38 Re: plan invalidation vs stored procedures
Previous Message Merlin Moncure 2008-08-06 18:33:39 Re: plan invalidation vs stored procedures