Horton

Re: BUG #15032: Segmentation fault when running a particular query

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Guo Xiang Tan <gxtan1990@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>
Date: 2018-01-27T01:42:47Z
Lists: pgsql-bugs

Attachments

Guo Xiang Tan <gxtan1990@gmail.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

Commits

  1. Avoid crash during EvalPlanQual recheck of an inner indexscan.

  2. Fix parallel index and index-only scans to fall back to serial.