| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| 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:42:43 |
| Message-ID: | pwoihbvv32uyckgdsotzzatvkfi2guto2frfxo6rlnzk4fqah7@ohl47fm6yevu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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).
I started looking at the patch because I got worried it was introducing
dynamic rescoring or such, which has potential of introducing situations where
we'll never get to some relations or such. But I don't think that is in this
patch.
Greetings,
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2026-11-02 17:44:19 | Re: Internal error codes triggered by regression tests and user queries, take 2 |
| Previous Message | Tomas Vondra | 2026-11-02 17:39:40 | Re: [PATCH] Fix segmentation fault caused by reentrancy in RI_Fkey_cascade_del (ri_triggers.c) |