| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: assert in nested SQL procedure call in current HEAD |
| Date: | 2018-06-12 15:25:37 |
| Message-ID: | 5469a23e-1a38-b162-bc47-e637e5b6b2fd@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/12/18 10:03, Andrew Gierth wrote:
>>>>>> "Peter" == Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>
> Peter> The problem with these nested procedure calls is that if the
> Peter> nested call
>
> Did you miss the fact that the issue only occurs when the top-level
> procedure does a rollback? The problem is not with nested calls, but
> rather with the fact that commit or rollback is leaving ActiveSnapshot
> unset, which is (as Tom pointed out at the linked post) not the expected
> condition inside PL code.
We need that so that we can run things like SET TRANSACTION ISOLATION.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raphael Medaer | 2018-06-12 15:28:51 | Attempt to fix inheritance limitations: unique and foreign key constraints |
| Previous Message | Andrew Dunstan | 2018-06-12 15:15:38 | Re: late binding of shared libs for C functions |