From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ondřej Bouda <obouda@email.cz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Tue, 06 Nov 2018 16:47:20 -0500
Message-ID: <4375.1541540840@sss.pgh.pa.us> (raw)
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>
=?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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, obouda@email.cz, alvherre@2ndquadrant.com, pgsql-hackers@lists.postgresql.org, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <4375.1541540840@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox