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

From Amit Kapila
Subject Re: Hitting CheckRelationLockedByMe() ASSERT with force_generic_plan
Date
Msg-id CAA4eK1J6dCfRE-hJXJbnBwy75_4wFJaWQmTUgunArJTytu7d0w@mail.gmail.com
Whole thread Raw
In response to Re: Hitting CheckRelationLockedByMe() ASSERT with force_generic_plan  (Rushabh Lathia <rushabh.lathia@gmail.com>)
List pgsql-hackers
On Fri, Dec 14, 2018 at 11:32 AM Rushabh Lathia
<rushabh.lathia@gmail.com> wrote:
>
> While looking code further around this, I realized that we need
> similar kind of fix for bitmap as well as index only scan as well.
>

I think if we want to move forward with this patch, we need to first
investigate the deadlock hazard mentioned by Tom in other related
thread [1].   I and others have also responded on that thread, see if
you can respond to it.

[1] - https://www.postgresql.org/message-id/3046.1542990312%40sss.pgh.pa.us

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Sergei Kornilov
Date:
Subject: Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name
Next
From: Tomas Vondra
Date:
Subject: explain plans with information about (modified) gucs