public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nathan Bossart <[email protected]>
To: wenhui qiu <[email protected]>
Cc: Shinya Kato <[email protected]>
Cc: [email protected]
Subject: Re: enhance wraparound warnings
Date: Fri, 20 Mar 2026 14:16:42 -0500
Message-ID: <ab2dGqvlPLoihxBK@nathan> (raw)
In-Reply-To: <CAGjGUALHrAWK4jDK9xvwBHg-5Qw9bZF9yqNHHAXcVQrce8KJtw@mail.gmail.com>
References: <aRdhSSFb9zZH_0zc@nathan>
	<CAOzEurR9vD9kZ7=LAYqTDRju8wvCyvyEeiEtJVHJ_C6wH1u_MA@mail.gmail.com>
	<aadFHfocomG20wgM@nathan>
	<aatR8GUfwWA7ciFV@nathan>
	<CAGjGUALHrAWK4jDK9xvwBHg-5Qw9bZF9yqNHHAXcVQrce8KJtw@mail.gmail.com>

On Mon, Mar 09, 2026 at 08:08:54PM +0800, wenhui qiu wrote:
> Thank you for working on this. The path LGTM,...

Thanks for looking.  Committed.

> ...But I have a small request,There
> are many reasons why the table's age can’t be frozen. Now have a path that
> can report the reason to users(https://commitfest.postgresql.org/patch/6188/).
> Would you be interested in reviewing it? I think we should tell users the
> root cause of why the age can’t be reduced, so they can clearly understand
> where the issue is.I think we should not only tell users that the XID is
> close to wraparound, but also report why this causes the table‘s age to be
> unable to freeze.

Thanks for alerting me to this patch.

-- 
nathan

view thread (20+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: enhance wraparound warnings
  In-Reply-To: <ab2dGqvlPLoihxBK@nathan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox