Re: [PATCH] Periodically refresh database frozen IDs during autovacuum

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Periodically refresh database frozen IDs during autovacuum
Date: 2026-11-02 17:50:52
Message-ID: aujNfHlv1_NAQLYf@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 02, 2026 at 12:42:43PM -0500, Andres Freund wrote:
> On 2026-11-02 10:48:22 -0600, Nathan Bossart wrote:
>> On Tue, Nov 03, 2026 at 12:40:15AM +0800, Jingtang Zhang wrote:
>> > This patch periodically refreshes the database's frozen-ID horizons
>> > between tables.
>>
>> My first question is why would we only refresh one score component and not
>> all of them?
>
> I think this isn't really about the scoring, it's about updating datfrozenxid
> more often (i.e. basically *writing* progress more often).

My bad, I clearly misunderstood the proposal.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2026-11-02 17:57:53 Re: Improve cube GiST page splits
Previous Message Kirill Reshke 2026-11-02 17:44:19 Re: Internal error codes triggered by regression tests and user queries, take 2