That was quick. Applied the 91715e82932665 commit directly against the 9.2=
.4 pgdg source, fix works great. Test data and the original breaking produ=
ction queries run fine for me. Thank you very much!
-joel
On May 9, 2013, at 6:19 PM, Tom Lane wrote:
> jroller@rjobrien.com writes:
>> We've come across a specific query and query plan that causes a repeatab=
le
>> segmentation fault on the postgresql backend.
>=20
> Ah, I see it: gistrescan() is trying to preserve the per-scankey
> fn_extra values to allow caching, but what it's doing does not work
> if more than one scankey refers to the same consistentFn, ie, the
> same index column. A bit surprising we've not seen this before,
> because I think that code has been like that for awhile.
>=20
> Will fix, thanks for the report!
>=20
> regards, tom lane
