On Sat, Jul 12, 2025 at 12:32:31AM +0300, Aleksander Alekseev wrote:
> Good catch. I don't see any reason why we might want to keep ckptFullXid.
> Also I checked if there are any references left to this field - there are
> none.
Thanks, committed.
--
nathan
Hi Nathan,
> I just noticed $SUBJECT. This seems to be an oversight in commit 2fc7af5,
> which simultaneously combined ckptXidEpoch and ckptXid into ckptFullXid
and
> removed the only use of that information, i.e., GetNextXidAndEpoch(). Any
> objections if I remove it now?
Good catch. I don't s
I just noticed $SUBJECT. This seems to be an oversight in commit 2fc7af5,
which simultaneously combined ckptXidEpoch and ckptXid into ckptFullXid and
removed the only use of that information, i.e., GetNextXidAndEpoch(). Any
objections if I remove it now?
--
nathan
>From 19a915582492a2a6a02a0c98
