| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Emiliano Saenz <saenz(dot)emi(dot)jos(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: The Curious Case of the Table-Locking UPDATE Query |
| Date: | 2021-07-08 17:42:24 |
| Message-ID: | 20210708174224.GA9739@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jul 08, 2021 at 02:35:33PM -0300, Emiliano Saenz wrote:
> Attach the files.
The pg_locks file doesn't show any access exclusive locks on any table?
=$ awk -F, 'NR==1 || $13 == "AccessExclusiveLock"' pg_locks.csv
Locktype,Database,Relation,Page,Tuple,Virtualxid,Transactionid,Classid,Objid,Objsubid,Virtualtransaction,Pid,Mode,Granted,Fastpath
tuple,248043888,248044255,213071,39,NULL,NULL,NULL,NULL,NULL,198/814,21038,AccessExclusiveLock,f,f
tuple,248043888,248044255,213071,39,NULL,NULL,NULL,NULL,NULL,34/90197,21187,AccessExclusiveLock,t,f
tuple,248043888,248044255,213071,39,NULL,NULL,NULL,NULL,NULL,132/957,21007,AccessExclusiveLock,f,f
As you can see all the AccessExclusive locks are on tuples (rows).
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atul Kumar | 2021-07-08 18:55:10 | Re: optimization issue |
| Previous Message | Emiliano Saenz | 2021-07-08 17:35:33 | Re: The Curious Case of the Table-Locking UPDATE Query |