From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ondřej Bouda <obouda(at)email(dot)cz> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: backend crash on DELETE, reproducible locally |
Date: | 2018-11-06 21:47:20 |
Message-ID: | 4375.1541540840@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda(at)email(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-11-06 21:54:49 | Re: backend crash on DELETE, reproducible locally |
Previous Message | Ondřej Bouda | 2018-11-06 21:37:32 | Re: backend crash on DELETE, reproducible locally |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-11-06 21:52:44 | Re: Special role for subscriptions |
Previous Message | Andrew Gierth | 2018-11-06 21:43:38 | Re: First-draft release notes for back-branch releases |