From: Ondřej Bouda <obouda@email.cz>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: 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, 6 Nov 2018 22:37:32 +0100
Message-ID: <fc1fde8f-2e1d-3f8d-a583-82ba383c7fd2@email.cz> (raw)
In-Reply-To: <2877.1541538838@sss.pgh.pa.us>
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>
> 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"
Creating a new index is wrong, too:
# CREATE INDEX schedulecard_overlap_idx2
ON public.schedulecard USING gist
(scheduletemplate_id, (period_day::integer % 7), timerange)
WITH (recheck_on_update = FALSE);
ERROR: unrecognized parameter "recheck_on_update"
It only succeeds if not USING gist:
# CREATE INDEX schedulecard_overlap_idx2
ON public.schedulecard
(scheduletemplate_id, (period_day::integer % 7), timerange)
WITH (recheck_on_update = FALSE);
CREATE INDEX
Is there any other workaround for a gist index, please?
Maybe we will just drop the index until the bug gets fixed - better slow
queries than crashing servers...
Thanks,
Ondřej Bouda
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: obouda@email.cz, tgl@sss.pgh.pa.us, 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>
* 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