| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Satalabaha Postgres <satalabaha(dot)postgres(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: backend_xid and backend_xmin |
| Date: | 2022-12-08 20:46:12 |
| Message-ID: | 9565562b389eb3c105588d3c218907f84d0a2fa9.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sbob | 2022-12-08 21:36:27 | PostgreSQL Constraints and Foreign Keys - Dropping Tables |
| Previous Message | Gunnar Venaas | 2022-12-08 19:08:57 | RE: Using non-Super user with PgAmdin |