| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Maxim Orlov <orlovmg(at)gmail(dot)com> |
| Cc: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, Scott Ray <scott(at)scottray(dot)io>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Report oldest xmin source when autovacuum cannot remove tuples |
| Date: | 2026-11-19 04:36:44 |
| Message-ID: | CALj2ACVUxw9hfCW3mtMjcK9ictbpk8_cDTFEYek7vR5zeNVvpw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Wed, Nov 18, 2026 at 7:03 AM Maxim Orlov <orlovmg(at)gmail(dot)com> wrote:
>
> On Tue, 17 Nov 2026 at 01:05, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>>
>> Thanks for the updated patch. Sorry for the delay. I have been
>> thinking about how useful reporting the per-vacuum blocker will be
>> with the pg_xmin_horizon view proposed in the other thread. Why can't
>> users find the blockers with the view and the removable cutoff that is
>> already reported in the verbose log output?
>
> That's interesting. BTW, I do not see the pg_xmin_horizon patch CF entry.
Thanks for taking a look. Here it is
https://commitfest.postgresql.org/patch/7004 (in the Current CF).
--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-11-19 04:45:21 | Re: Per-table resync for logical replication subscriptions |
| Previous Message | vignesh C | 2026-11-19 04:35:29 | Re: [PATCH v1] Fix initial sync of zero-column published tables |