Re: Add contrib/pg_logicalsnapinspect - Mailing list pgsql-hackers

From shveta malik
Subject Re: Add contrib/pg_logicalsnapinspect
Date
Msg-id CAJpy0uB44r5dXv0KXe2xz5dyhwwq484=LYPOcVYrbcLHFxVEJA@mail.gmail.com
Whole thread Raw
In response to Re: Add contrib/pg_logicalsnapinspect  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
On Wed, Sep 25, 2024 at 11:01 PM Bertrand Drouvot
<bertranddrouvot.pg@gmail.com> wrote:
>
> Hi,
>
> On Wed, Sep 25, 2024 at 11:23:17AM +0530, shveta malik wrote:
> > + OUT catchange_xip xid[]
> >
> > One question, what is xid datatype, is it too int8? Sorry, could not
> > find the correct doc.
>
> I think that we can get the answer from pg_type:
>
> postgres=# select typname,typlen from pg_type where typname = 'xid';
>  typname | typlen
> ---------+--------
>  xid     |      4
> (1 row)
>
> > Since we are getting uint32 in Int64, this also needs to be accordingly.
>
> I think the way it is currently done is fine: we're dealing with TransactionId
> (and not with FullTransactionId). So, the Int64GetDatum() output would still
> stay in the "xid" range. Keeping xid in the .sql makes it clear that we are
> dealing with transaction ID.
>

Okay, got it. The 'xid' usage is fine then.

thanks
Shveta



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: CREATE INDEX regression in 17 RC1 or expected behavior?
Next
From: Yugo Nagata
Date:
Subject: Re: CREATE INDEX regression in 17 RC1 or expected behavior?