pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedbackend_xid and backend_xmin
2+ messages / 2 participants
[nested] [flat]
* backend_xid and backend_xmin
@ 2022-12-08 15:31 Satalabaha Postgres <satalabaha.postgres@gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: Satalabaha Postgres @ 2022-12-08 15:31 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi All,
I would like to understand the possible causes for backend_xmin getting
populated in pg_stat_activity. Can someone throw some light on this?
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: backend_xid and backend_xmin
@ 2022-12-08 20:46 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Satalabaha Postgres <satalabaha.postgres@gmail.com>
0 siblings, 0 replies; 2+ messages in thread
From: Laurenz Albe @ 2022-12-08 20:46 UTC (permalink / raw)
To: Satalabaha Postgres <satalabaha.postgres@gmail.com>; pgsql-admin@lists.postgresql.org
On Thu, 2022-12-08 at 21:01 +0530, Satalabaha Postgres wrote:
> I would like to understand the possible causes for backend_xmin getting
> populated in pg_stat_activity. Can someone throw some light on this?
"backend_xid" is set when the session has an open transaction that has
modified data and therefore got a transaction ID.
"backend_xmin" is set if there is an active snapshot held by the session:
- there is a running query
- there is an open transaction with an open cursor
- there is an open transaction with isolation level REPEATABLE READ or higher
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-12-08 20:46 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-12-08 15:31 backend_xid and backend_xmin Satalabaha Postgres <satalabaha.postgres@gmail.com>
2022-12-08 20:46 ` Laurenz Albe <laurenz.albe@cybertec.at>
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