From: Carlos Alves <carlos.alves@tecnisys.com.br>
To: pgsql-general@lists.postgresql.org
Subject: Question about tuple´s lock
Date: Tue, 24 Oct 2023 13:27:35 -0300
Message-ID: <2fa29bee5e4a7c369f54f02198423814@tecnisys.com.br> (raw)
Hi!
I need some help to understand why a transaction wiht a row delete
aquire a AccessExclusiveLock and a row update a ExclusiveLock.
To ilustrate, a made this scenario:
create table tblock
(
id int primary key,
value text
);
insert into tblock values (1, 'somevalue');
First start Transaction 1:
begin;
update tblock set value = 'othervalue' where id = 1;
-- keep this transaction opened
After, start Transaction 2:
begin;
update tblock set value = 'onemorevalue' where id = 1;
-- at this point, this transaction assumes a ExclusiveLock in the tuple;
-- keep this transaction opend
Then, start Transaction 3:
begin;
update tblock set value = 'lastofthevalues' where id = 1;
-- here i can see this transaction trying to aquire a
AccessExclusiveLock in this tuple
So, my question is: why a delete row requires a AccessExclusiveLock in
the tuple insteead of ExclusiveLock?
Bellow, a image of a query over pg_locks:
PostgreSQL version: 13
OS: Centos 7
Thanks in advance.
--
Carlos Alves
Especialista
Sia Trecho 08, lotes 245 / 255 / 265 || +55 (61) 3039-9700
71205-080 || Guará || Brasília, DF 0800-6020097
www.tecnisys.com.br [1]
Links:
------
[1] http://www.tecnisys.com.brAttachments:b9879537.png (image/png, 73.1K) downloadview imagef62593aa.gif (image/gif, 43B) downloadview image04237a95.gif (image/gif, 3.1K) downloadview image
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: carlos.alves@tecnisys.com.br
Subject: Re: Question about tuple´s lock
In-Reply-To: <2fa29bee5e4a7c369f54f02198423814@tecnisys.com.br>
References: <2fa29bee5e4a7c369f54f02198423814@tecnisys.com.br>
* 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