Re: Decoupling our alignment assumptions about int64 and double

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Decoupling our alignment assumptions about int64 and double
Date: 2026-02-05 23:49:40
Message-ID: 1666149.1770335380@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> I am pretty unhappy about that, I think the test and rules are just about
>> incomprehensible. I wonder if we ought to instead just redefine float8 to be
>> be aligned to 8 bytes, leaving double alone.

> I thought about that, but it seemed like there'd be nothing stopping
> people from declaring a catalog column as "double" rather than
> "float8" and thus falling into the trap anyway. I suppose we could
> put a check for that into Catalog.pm, though.

No, scratch that: the real objection is that we can't do that unless
we are willing to break pg_upgrade on AIX. The catalogs can't have
different alignment rules than user tables do. Now, maybe we're
willing to go there, but it's not a pleasant prospect.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-02-06 00:01:52 Re: client_connection_check_interval default value
Previous Message Fujii Masao 2026-02-05 23:42:42 Re: client_connection_check_interval default value