| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL, RAISE and error context |
| Date: | 2015-01-26 13:02:53 |
| Message-ID: | 54C63AFD.2050307@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/26/15 1:44 PM, Pavel Stehule wrote:
> 2015-01-26 13:39 GMT+01:00 Marko Tiikkaja <marko(at)joh(dot)to>:
>> On 1/26/15 1:14 PM, Pavel Stehule wrote:
>>> I afraid about some unexpected side effects of your proposal if somebody
>>> mix languages - these side effects should not be critical
>>>
>>
>> I have no idea what you're talking about. What kind of side effects?
>>
>
> what will be a error context if plpgsql calls a plperl function that raises
> a exception
> what will be a error context if plperl calls a plpgsql functions that
> raises a exception
I fail to see the point. How would that be different from what happens
today? Remember, PL/PgSQL only suppresses the *topmost* stack frame,
and only when using RAISE from within a PL/PgSQL function.
.m
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2015-01-26 13:06:35 | Re: fix typo in guc.c |
| Previous Message | Sawada Masahiko | 2015-01-26 12:56:11 | fix typo in guc.c |