Re: Improper use about DatumGetInt32 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Improper use about DatumGetInt32
Date
Msg-id a3c0e62c-2035-e178-4858-fee72c5193df@enterprisedb.com
Whole thread Raw
In response to Re: Improper use about DatumGetInt32  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Improper use about DatumGetInt32  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2021-01-08 10:21, Peter Eisentraut wrote:
> I think on 64-bit systems it's actually safe, but on 32-bit systems
> (with USE_FLOAT8_BYVAL), if you use the new binaries with the old
> SQL-level definitions, you'd get the int4 that is passed in interpreted
> as a pointer, which would lead to very bad things.  So I think we need
> to create new functions with a different C symbol.  I'll work on that.

Updated patch that does that.

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Proposal: Global Index
Next
From: Bruce Momjian
Date:
Subject: Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)