Re: Pie-in-sky dreaming about reworking tuple layout entirely - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Pie-in-sky dreaming about reworking tuple layout entirely
Date
Msg-id b42b73150610031406v4ac79e1ak7b8d43109a8f0d8a@mail.gmail.com
Whole thread Raw
In response to Pie-in-sky dreaming about reworking tuple layout entirely  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Pie-in-sky dreaming about reworking tuple layout entirely  (Jim Nasby <jimn@enterprisedb.com>)
List pgsql-hackers
On 10/3/06, Gregory Stark <stark@enterprisedb.com> wrote:
>
> I can't shake the feeling that merely tweaking the way our varlenas work with
> a shortvarlena or with compressed varlena headers is missing the real source
> of our headaches. It seems very strange to me to be trying to step through a
> tuple with length bits at the head of every field. It's a lot of work spent
> dealing with a terribly inconvenient format when we can pick the format to be
> whatever we like.

one advantage of the current system is that columns with nulls do not
require any storage.  so you can alter table add column for free on a
really big table.  ISTM that your approch would require moving all the
static fields in if you added a static field regardless, right?

merlin


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: PG qsort vs. Solaris
Next
From: Bruce Momjian
Date:
Subject: Re: PG qsort vs. Solaris