Message-ID: <3a4e7019df93301b82a98ddbfa73d31170d03a45.camel@cybertec.at>
Subject: Re: Different Lock Behavior With Create and Drop Foreign Key
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Virendra Kumar <viru_7683@yahoo.com>, Pgsql-general General
	 <pgsql-general@postgresql.org>
Date: Fri, 10 Apr 2020 07:27:37 +0200
In-Reply-To: <834603375.3470346.1586482852542@mail.yahoo.com>
References: <834603375.3470346.1586482852542.ref@mail.yahoo.com>
	 <834603375.3470346.1586482852542@mail.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 2020-04-10 at 01:40 +0000, Virendra Kumar wrote:
> Here is test case.
> ----
> create table testx
> (
>     v_code character varying(32),
>     client_id bigint
> );
> alter table testx add constraint testx_pkey primary key (v_code);
> 
> create table testy
> (
>     dxid bigint,
>     v_code character varying(32)
> );
> alter table testy add constraint testy_pkey primary key (dxid);
> create index on testy (v_code);
> 
> Let's begin two session, in session1 I am going begin a transaction and run select on parent table:
> 
> Session1
> ----
> begin;
> select * from testx;
> 
> 
> On another session let's call session2, I am running create FK on second table
> 
> Session2
> ---
> alter table testy add constraint testy_fkey foreign key (v_code) references testx(v_code); <--This works.
> alter table testy drop constraint testy_fkey; <--Hangs

That is because foreign keys are implemented with system triggers, some of which
are defined on the target table.

Now CREATE TRIGGER does not require an ACCESS EXCLUSIVE lock, but DROP TRIGGER does.

Session 1 holds an ACCESS SHARE lock on the table, which conflicts only with ACCESS EXCLUSIVE.

So creating the foreign key works, but dropping it hangs when the triggers are dropped.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com