Re: enhance wraparound warnings

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: enhance wraparound warnings
Date: 2026-03-09 12:08:54
Message-ID: CAGjGUALHrAWK4jDK9xvwBHg-5Qw9bZF9yqNHHAXcVQrce8KJtw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Nathan Bossart
> Barring additional feedback or objections, I'm planning to commit this in
> the next week or two.
Thank you for working on this. The path LGTM,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

On Sat, Mar 7, 2026 at 6:15 AM Nathan Bossart <nathandbossart(at)gmail(dot)com>
wrote:

> Barring additional feedback or objections, I'm planning to commit this in
> the next week or two.
>
> --
> nathan
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-03-09 12:23:09 Re: Emitting JSON to file using COPY TO
Previous Message Akshay Joshi 2026-03-09 12:08:01 Re: [PATCH] Add pg_get_database_ddl() function to reconstruct CREATE DATABASE statement