Postgres Pro
Downloads
Home   >   mailing lists

Re: Should we add xid_current() or a int8->xid cast? - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Should we add xid_current() or a int8->xid cast?
Date
Msg-id CA+hUKGLgE56triYvf4ocPH7e=oJa-0RLPxpDSLD913vXqdK0+w@mail.gmail.com
Whole thread Raw
In response to Re: Should we add xid_current() or a int8->xid cast?  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
Tree view 
On Fri, Apr 17, 2020 at 3:44 AM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
> Hmm, I should have spoken sooner...
>
> src/backend/replication/walsender.c:static bool TransactionIdInRecentPast(TransactionId xid, uint32 epoch);
> src/backend/utils/adt/xid8funcs.c:TransactionIdInRecentPast(FullTransactionId fxid, TransactionId *extracted_xid)
>
> I don't care much for having two different functions with the same name and related semantics but different argument
types.

Maybe that's not ideal, but it's not because of this patch.  Those
functions are from 5737c12df05 and 857ee8e391f.

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: fixing old_snapshot_threshold's time->xid mapping
Next
From: Andres Freund
Date:
Subject: Re: xid wraparound danger due to INDEX_CLEANUP false