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

From Shinya Kato
Subject Re: Report oldest xmin source when autovacuum cannot remove tuples
Date
Msg-id CAOzEurRAiBfN-f5juywYzjS+5rWXTSSr3jaVaCJ39TJnwvUimQ@mail.gmail.com
Whole thread
In response to Outdated 'VALUES' information  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: Report oldest xmin source when autovacuum cannot remove tuples
Re: Report oldest xmin source when autovacuum cannot remove tuples
List pgsql-hackers
On Sat, May 23, 2026 at 2:22 PM Shinya Kato <shinya11.kato@gmail.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

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: postgres_fdw: use_scram_passthrough on user mapping is ignored when also set on server
Next
From: vignesh C
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication