| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | julian(dot)schauder(at)gmx(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15703: Segfault in cancelled CALL-Statements |
| Date: | 2019-03-20 16:07:47 |
| Message-ID: | 9112.1553098067@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> Poking around a bit, it seems like this is a thinko in HoldPinnedPortals:
> it's not considering the possibility of a failure during HoldPortal().
> In your test the failure is triggered by query cancel, but an ordinary
> execution error while finishing out a cursor's calculations would be
> a problem too.
Pursuant to which observation, here's a fully self-contained test case.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| bug-15703-reproducer.sql | text/plain | 223 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-03-20 16:26:48 | BUG #15707: Incorrect timing information in EXPLAIN ANALYZE output |
| Previous Message | Tom Lane | 2019-03-20 15:56:13 | Re: BUG #15703: Segfault in cancelled CALL-Statements |