From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Virendra Kumar <viru_7683@yahoo.com>
To: Pgsql-general General <pgsql-general@postgresql.org>
Subject: Re: Different Lock Behavior With Create and Drop Foreign Key
Date: Fri, 10 Apr 2020 07:27:37 +0200
Message-ID: <3a4e7019df93301b82a98ddbfa73d31170d03a45.camel@cybertec.at> (raw)
In-Reply-To: <834603375.3470346.1586482852542@mail.yahoo.com>
References: <834603375.3470346.1586482852542.ref@mail.yahoo.com>
<834603375.3470346.1586482852542@mail.yahoo.com>
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
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: laurenz.albe@cybertec.at, viru_7683@yahoo.com
Subject: Re: Different Lock Behavior With Create and Drop Foreign Key
In-Reply-To: <3a4e7019df93301b82a98ddbfa73d31170d03a45.camel@cybertec.at>
* 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