From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
        pgsql-hackers@lists.postgresql.org, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-reply-to: <fc1fde8f-2e1d-3f8d-a583-82ba383c7fd2@email.cz>
References: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql>
 <33d144b9-5208-8d32-7e95-94ed4d2931b8@email.cz>
 <450.1541535425@sss.pgh.pa.us>
 <134c09b5-3eb0-bafd-2aeb-f383e1e21b8a@email.cz>
 <2432.1541538215@sss.pgh.pa.us> <2877.1541538838@sss.pgh.pa.us>
 <fc1fde8f-2e1d-3f8d-a583-82ba383c7fd2@email.cz>
Comments: In-reply-to =?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz>
	message dated "Tue, 06 Nov 2018 22:37:32 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <4374.1541540840.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Tue, 06 Nov 2018 16:47:20 -0500
Message-ID: <4375.1541540840@sss.pgh.pa.us>
Precedence: bulk

=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz> writes:
>> Ondřej, as a short-term workaround you could prevent the crash
>> by setting that index's recheck_on_update property to false.

> Thanks for the tip. I am unsuccessful using it, though:
> # ALTER INDEX public.schedulecard_overlap_idx SET (recheck_on_update = 
> FALSE);
> ERROR:  unrecognized parameter "recheck_on_update"

Oh, for crying out loud.  That's yet a different bug.
I'm not sure that it's the fault of the recheck_on_update
feature proper though; it might be a pre-existing bug in
the reloptions code.  Looks like somebody forgot to list
RELOPT_KIND_GIST in RELOPT_KIND_INDEX, but is that the
fault of commit c203d6cf8 or was it busted before?

			regards, tom lane