Re: AIX support - alignment issues - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: AIX support - alignment issues
Date
Msg-id 82efc9f6-d8d6-7226-b167-b807dce568cd@enterprisedb.com
Whole thread Raw
In response to Re: AIX support - alignment issues  (Andres Freund <andres@anarazel.de>)
Responses Re: AIX support - alignment issues
List pgsql-hackers
On 05.07.22 07:31, Andres Freund wrote:
> On 2022-07-02 11:33:54 -0700, Andres Freund wrote:
>> If we decide we want to continue supporting AIX we should bite the bullet and
>> add a 64bit-int TYPALIGN_*. It might be worth to translate that to bytes when
>> building tupledescs, so we don't need more branches (reducing them compared to
>> today).
> 
> I just thought an easier way - why don't we introduce a 'catalog_double'
> that's defined to be pg_attribute_aligned(whatever-we-need) on AIX? Then we
> can get rid of the manually enforced alignedness and we don't need to contort
> catalog order.

Isn't the problem that on AIX, double and int64 have different alignment 
requirements, and we just check the one for double and apply it to 
int64?  That ought to be fixable by two separate alignment checks in 
configure and a new alignment letter for pg_type.



pgsql-hackers by date:

Previous
From: "Anton A. Melnikov"
Date:
Subject: Re: [PATCH] Fix pg_upgrade test from v10
Next
From: Andres Freund
Date:
Subject: Re: AIX support - alignment issues