Chapman Flack writes:
> On 10/20/19 14:47, Tom Lane wrote:
>> Probably the statement in CREATE TYPE is too strong. There are, I
>> believe, still machines in the buildfarm where maxalign is just 4.
> So just closing the circle on this, the low-down seems to be that
> the alignments called s, i,
On 10/20/19 14:47, Tom Lane wrote:
> Chapman Flack writes:
>> 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 m
Chapman Flack 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_typ
Hi,
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 alignm
