From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TOASTing smaller things |
Date: | 2007-03-22 17:19:37 |
Message-ID: | C22808B9.2A253%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas,
On 3/22/07 9:40 AM, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> wrote:
> Wouldn't it be enough to enable having the toast table on a different
> table space?
Yes, but the ultimate goal would allow the allocation of a storage mechanism
that is unique to each column. The most frequently used mechanism for our
customers would likely be to have each column associated with it's own
internal relation (like a separate TOAST table), which puts each column into
it's own dense page storage.
Beside the advantages of separating out keys columns from data columns,
compression and encryption approaches that use column packed data are much
more effective.
As Tom points out there are complications WRT update, access, etc that need
to be worked out to support this, but it's an important capability to have
IMO.
- Luke
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-22 17:41:26 | Re: CREATE INDEX and HOT - revised design |
Previous Message | Alvaro Herrera | 2007-03-22 17:08:28 | Re: Regression failure in PL/Tcl |