| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Marko Kreen" <markokr(at)gmail(dot)com> |
| Cc: | "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:13:58 |
| Message-ID: | b42b73150808061113j3d8e73fala168b0e970151f62@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Pihlak | 2008-08-06 18:28:22 | Patch: plan invalidation vs stored procedures |
| Previous Message | Tom Lane | 2008-08-06 16:59:54 | Re: Parsing of pg_hba.conf and authenticationinconsistencies |