Re: Physical column size - Mailing list pgsql-general

From Tom Lane
Subject Re: Physical column size
Date
Msg-id 420.1141397627@sss.pgh.pa.us
Whole thread Raw
In response to Re: Physical column size  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Peter Eisentraut <peter_e@gmx.net> writes:
> An int4 field is required to be aligned at a 4-byte boundary internally, so
> there are 3 bytes wasted between tmp_A.c and tmp_A.i.  If you switch the
> order of the fields you should see space savings.

Probably not, because the row-as-a-whole has alignment requirements too.
In this example you'll just move the pad bytes from one place to
another.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres automatically inserts chr(13) whenever chr(10) is inserted
Next
From: "Just Someone"
Date:
Subject: Re: SELinux strangeness with 8.1.2 and 8.1.3