Re: documentation inconsistent re: alignment - Mailing list pgsql-hackers

From Tom Lane
Subject Re: documentation inconsistent re: alignment
Date
Msg-id 10248.1571597277@sss.pgh.pa.us
Whole thread Raw
In response to documentation inconsistent re: alignment  (Chapman Flack <chap@anastigmatix.net>)
Responses Re: documentation inconsistent re: alignment
List pgsql-hackers
Chapman Flack <chap@anastigmatix.net> writes:
> The documentation for CREATE TYPE has this to say about alignment:

> "The alignment parameter specifies the storage alignment required for the
> data type. The allowed values equate to alignment on 1, 2, 4, or 8 byte
> boundaries."

> ... while the documentation for pg_type has:

>     "c = char alignment, i.e., no alignment needed.
>     s = short alignment (2 bytes on most machines).
>     i = int alignment (4 bytes on most machines).
>     d = double alignment (8 bytes on many machines, but by no means all)."

> so, in 2019, are the alignments weaselly and variable, or are they 1,2,4,8?

Probably the statement in CREATE TYPE is too strong.  There are, I
believe, still machines in the buildfarm where maxalign is just 4.

            regards, tom lane



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Ordering of header file inclusion
Next
From: Andrew Dunstan
Date:
Subject: Re: configure fails for perl check on CentOS8