Re: Converting MySQL tinyint to PostgreSQL - Mailing list pgsql-general

From Dawid Kuroczko
Subject Re: Converting MySQL tinyint to PostgreSQL
Date
Msg-id 758d5e7f05071817027773a1f@mail.gmail.com
Whole thread Raw
In response to Re: Converting MySQL tinyint to PostgreSQL  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
Responses Re: Converting MySQL tinyint to PostgreSQL
Re: Converting MySQL tinyint to PostgreSQL
List pgsql-general
On 7/18/05, Lincoln Yeoh <lyeoh@pop.jaring.my> wrote:
> However, maybe padding for alignment is a waste on the disk - disks being
> so much slower than CPUs (not sure about that once the data is in memory ).
> Maybe there should be an option to reorder columns so that less space is
> wasted.

Out of curiosity, do I understand right that if I create table

CREATE TABLE sample1 (
    a boolean,
    b int,
    c boolean
);

...it will take more storage than:

CREATE TABLE sample2 (
    b int,
    a boolean,
    c boolean
);

...I don't think such ordering should matter, but I would like to know
how it really is. :)

   Regards,
       Dawid

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Composite type within a composite type?
Next
From: "Joshua D. Drake"
Date:
Subject: Re: index row size exceeds btree maximum, 2713 - Solutions?