Re: Optimize SnapBuildPurgeOlderTxn: use in-place compaction instead of temporary array

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: Xuneng Zhou <xunengzhou(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Optimize SnapBuildPurgeOlderTxn: use in-place compaction instead of temporary array
Date: 2025-10-20 23:31:05
Message-ID: aPbGOWbMrHXgnY6j@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 18, 2025 at 01:59:40PM +0500, Kirill Reshke wrote:
> Indeed, these changes look correct.
> I wonder why b89e151054a0 did this place this way, hope we do not miss
> anything here.

Perhaps a lack of time back in 2014? It feels like an item where we
would need to research a bit some of the past threads, and see if this
has been discussed, or if there were other potential alternatives
discussed. This is not saying that what you are doing in this
proposal is actually bad, but it's a bit hard to say what an
"algorithm" should look like in this specific code path with XID
manipulations. Perhaps since 2014, we may have other places in the
tree that share similar characteristics as what's done here.

So it feels like this needs a bit more historical investigation first,
rather than saying that your proposal is the best choice on the table.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-10-20 23:44:48 Re: Fix lag columns in pg_stat_replication not advancing when replay LSN stalls
Previous Message Michael Paquier 2025-10-20 23:23:45 Re: Skip unregistered custom kinds on stats load