From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, 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-29 11:52:23 |
Message-ID: | 68b4906f-f7f6-fa23-7fb4-4449cb0f0857@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/27/18 18:51, Peter Eisentraut wrote:
> On 6/27/18 17:44, Andres Freund wrote:
>> This hasn't progressed in a while. Peter, since you committed the
>> relevant change, could you update us please?
>
> I've been on vacation for a bit. I will work on this next. I hope to
> have a solution in a few days.
Proposed patch attached.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Fix-assert-in-nested-SQL-procedure-call.patch | text/plain | 5.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-06-29 11:56:12 | Re: Failed assertion due to procedure created with SECURITY DEFINER option |
Previous Message | amul sul | 2018-06-29 11:07:46 | Failed assertion due to procedure created with SECURITY DEFINER option |