| From: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> |
|---|---|
| To: | Japin Li <japinli(at)hotmail(dot)com> |
| Cc: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(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-05-23 06:00:33 |
| Message-ID: | CAOzEurRAiBfN-f5juywYzjS+5rWXTSSr3jaVaCJ39TJnwvUimQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 23, 2026 at 2:22 PM Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> wrote:
> Additionally, I forgot to update meson.build, which caused the tests
> to fail. I have fixed that in the attached patch.
Oops, I made a slight mistake. Fixed.
--
Best regards,
Shinya Kato
NTT OSS Center
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Report-oldest-xmin-blocker-when-VACUUM-cannot-rem.patch | application/octet-stream | 26.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2026-05-23 06:10:40 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Shinya Kato | 2026-05-23 05:22:48 | Re: Report oldest xmin source when autovacuum cannot remove tuples |