Re: Smaller data types use same disk space

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "McGehee, Robert" <Robert(dot)McGehee(at)geodecapital(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Smaller data types use same disk space
Date: 2012-07-25 22:20:08
Message-ID: CABs1bs2aNgaeWFFKnES7TFZqcK29iBiQrhVLDxzrc-aiyfTbxQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 25, 2012 at 1:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "McGehee, Robert" <Robert(dot)McGehee(at)geodecapital(dot)com> writes:
>> One might even imagine a future version of PostgreSQL using an
>> efficient disk layout that may not match the table layout in order to
>> avoid wasted space from padding.
>
> Yeah, this has been discussed multiple times. The sticking point is
> the extra infrastructure needed to have a physical column numbering
> different from the user-visible numbering, and the 100% certainty of
> introducing a lot of bugs due to bits of code using one type of column
> number where they should have used the other. We'll probably get it
> done someday, but don't hold your breath ...

Has there been any discussion of providing the ability to re-order
table columns through an ALTER TABLE command? I would love to see
this; when I add in a new column, I often want to put it next to
something just to be more visually appealing when I'm running ad-hoc
queries. It could potentially address this problem as well.

Mike

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2012-07-25 22:49:25 Re: Smaller data types use same disk space
Previous Message Gavin Flower 2012-07-25 21:17:51 Re: Smaller data types use same disk space