Re: Hitting CheckRelationLockedByMe() ASSERT with force_generic_plan - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hitting CheckRelationLockedByMe() ASSERT with force_generic_plan
Date
Msg-id 1413.1542947433@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hitting CheckRelationLockedByMe() ASSERT with force_generic_plan  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
David Rowley <david.rowley@2ndquadrant.com> writes:
> On Thu, 22 Nov 2018 at 22:33, Rushabh Lathia <rushabh.lathia@gmail.com> wrote:
>> Now, to fix this issue either we need to hold proper lock before reaching
>> to ExecInitIndexScan() or teach ExecInitIndexScan() to take AccessShareLock
>> on the scan coming from CMD_DELETE.

> I'd say the following comment and code in nodeIndexscan.c is outdated:

I complained about this previously in

https://www.postgresql.org/message-id/19465.1541636036@sss.pgh.pa.us

but got nothing but crickets :-(

            regards, tom lane


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Should new partitions inherit their tablespace from their parent?
Next
From: David Rowley
Date:
Subject: Re: Inadequate executor locking of indexes