| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Guo Xiang Tan <gxtan1990(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: BUG #15032: Segmentation fault when running a particular query |
| Date: | 2018-01-27 01:42:47 |
| Message-ID: | 19519.1517017367@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Guo Xiang Tan <gxtan1990(at)gmail(dot)com> writes:
>> Unsurprisingly, the given info is not enough to reproduce the crash.
> We could only reproduce this on our production PostgreSQL cluster.
Since the problem occurs during EvalPlanQual, it'd only manifest when
the update touched a concurrently-updated row, which is why it's hard
to reproduce if you aren't deliberately trying to trigger it. But
I've been able to reproduce a crash at the same spot, and have made
a test case using the isolationtester infrastructure (attached).
I'll look into an actual fix tomorrow.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| epq-mark-crash-test.patch | text/x-diff | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-01-27 05:08:45 | BUG #15033: Segmentation fault running a query |
| Previous Message | Tom Lane | 2018-01-26 23:48:35 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |