| From: | arun chirappurath <arunsnmimt(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | pg_locks-exclusivelock for select queries |
| Date: | 2024-03-22 07:13:40 |
| Message-ID: | CAA23Sdt_abrMxJnZbJj5-rr5Z5C1J_UXUnORnbuCg8x3TZ6JoA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dear all,
I am running below query on a database. why is it creating a exclusive lock
on a virtualxid? I am running some SELECT queries and its creating an
ExclusiveLock in virtualxid? is this normal?
SELECT datname, pid, state, query, age(clock_timestamp(), query_start) AS
age
FROM pg_stat_activity
WHERE state <> 'idle'
--AND query NOT LIKE '% FROM pg_stat_activity %'
ORDER BY age;
|locktype
|database|relation|page|tuple|virtualxid|transactionid|classid|objid|objsubid|virtualtransaction|pid
|mode |granted|fastpath|waitstart|
|----------|--------|--------|----|-----|----------|-------------|-------|-----|--------|------------------|------|---------------|-------|--------|---------|
|relation |58,007 |12,073 | | | | | |
| |5/165 |21,912|AccessShareLock|true |true |
|
|virtualxid| | | | |5/165 | | |
| |5/165 |21,912|ExclusiveLock |true |true |
|
Thanks,
ACDBA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daulat | 2024-03-22 08:11:31 | Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen |
| Previous Message | Laurenz Albe | 2024-03-22 07:05:53 | Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen |