Request a Demo
Home   >   mailing lists

Re: Report oldest xmin source when autovacuum cannot remove tuples - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Report oldest xmin source when autovacuum cannot remove tuples
Date
Msg-id CAA5RZ0vEQ8aykyuoHRuyD=F+JhGEa0Zfy2vgVoEXtJfkt0Pt-A@mail.gmail.com
Whole thread
In response to Re: Report oldest xmin source when autovacuum cannot remove tuples  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Tree view 
> ComputeXidHorizons() already takes ProcArrayLock and has all the
> information about who is blocking the vacuum, so I think we can
> capture the blocker right there and get the reason almost for free,
> without a second scan.

This idea proved to result in incorrect information. See [1]

[1] https://www.postgresql.org/message-id/CAA5RZ0sjMgMo4Xg-niyyF-CpkQ_CK6uOfNKYT%3D9RmiBkAxQkbQ%40mail.gmail.com

--
Sami Imseih
Amazon Web Services (AWS)

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Report oldest xmin source when autovacuum cannot remove tuples
Next
From: Bharath Rupireddy
Date:
Subject: Re: Report index currently being vacuumed in pg_stat_progress_vacuum