Re: Cannot find a working 64-bit integer type on Illumos - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Cannot find a working 64-bit integer type on Illumos
Date
Msg-id CA+hUKG+AyuDcY5BX8uut2id11UDm-V+uwHz--o3h_iF1UKBhZA@mail.gmail.com
Whole thread Raw
In response to Re: Cannot find a working 64-bit integer type on Illumos  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Dec 5, 2024 at 10:55 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
> > ... We need this header to be readable without
> > any prior system headers, so I'm afraid we're all the way back to
> > making configure derive the name of a 64-bit type.
>
> Could another way be to read pg_config.h before postgres_ext.h?
> I think the current order was intentional, but maybe the
> disadvantages outweigh the advantages now.

Yeah I was just testing that idea :-)  I can't see why it needs to be
first, but was looking for what the original reason was...



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cannot find a working 64-bit integer type on Illumos
Next
From: James Hunter
Date:
Subject: Re: Possible integer overflow in bringetbitmap()