Re: All-visible pages with valid prune xid are confusing - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: All-visible pages with valid prune xid are confusing
Date
Msg-id CAAKRu_YmOFcg3jTc+q6jB1eTq6txpnkwORF44SKXwDqCQZW3ZQ@mail.gmail.com
Whole thread Raw
In response to Re: All-visible pages with valid prune xid are confusing  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: All-visible pages with valid prune xid are confusing
List pgsql-hackers
On Tue, Dec 2, 2025 at 12:49 PM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>
> Hmm. If the page has no prunable tuples left, it makes sense to set
> pd_prune_xid to InvalidTransactionId to avoid the useless round of
> pruning. In other cases, it would make sense to set it to some XID so
> that it gets pruned later. But a standby will only start pruning if it's
> later promoted to become a primary. At that point, all currently running
> transactions will be finished (except for prepared transactions).

What about on-access pruning during SELECT queries on a hot standby?

- Melanie



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Bug in amcheck?
Next
From: Andres Freund
Date:
Subject: Re: All-visible pages with valid prune xid are confusing