| From: | Virendra Kumar <viru_7683(at)yahoo(dot)com> |
|---|---|
| To: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | xact_start time set to very old value |
| Date: | 2020-08-10 06:05:12 |
| Message-ID: | 1930665427.2385958.1597039512032@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Team,
We have observed that xact_start time is null for some period and suddenly it populates to very old value. We have a query which runs every minute to report any transactions running for long time. That query reports nothing continuously for a minute before and suddenly it reports one transaction which is running for more than one day. Is there something wrong here in populating xact_start time in pg_stat_activity? Shall we go with any other approach to detect long running transaction in database? Can someone guide on this?
I went through a thread - https://www.postgresql.org/message-id/20140424101827.2714.39486%40wrigleys.postgresql.org but not sure where it concluded.
Appreciate your response.
We are using AWS RDS 11.4.
Regards,-Virendra
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashkar Dev | 2020-08-10 15:53:23 | UUID or auto-increment |
| Previous Message | Rama Krishnan | 2020-08-10 04:20:30 | Re: Need a depth information about bloat |