| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | bhargav kamineni <kbn98406(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: oldest xmin is far in the past :: BUT xmin is not available in system |
| Date: | 2022-04-19 15:38:49 |
| Message-ID: | 2555588.1650382729@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rob Sargent <robjsargent(at)gmail(dot)com> writes:
> On 4/19/22 00:06, David G. Johnston wrote:
>> On Monday, April 18, 2022, bhargav kamineni <kbn98406(at)gmail(dot)com> wrote:
>> It seems vacuum is behaving somewhat weird on postgres database ,
>> observing below HINTS on the vacuum logs
>> WARNING: oldest xmin is far in the past
> This site has lots of useful queries for this sort of issue:
> https://www.shanelynn.ie/postgresql-find-slow-long-running-and-blocked-queries.
> I think you're looking for a very old transaction that is probably not
> going to finish, must be terminated.
Yeah, that. Manual vacuuming isn't going to help until you get rid
of the old open transaction. Look into pg_prepared_xacts and
pg_stat_activity.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-04-19 15:48:29 | Re: oldest xmin is far in the past :: BUT xmin is not available in system |
| Previous Message | Justin Pryzby | 2022-04-19 13:39:28 | Re: Fwd: Declarative partitioning and partition pruning/check (+postgis) |