Re: TOASTing smaller things
| От | Chris Browne |
|---|---|
| Тема | Re: TOASTing smaller things |
| Дата | |
| Msg-id | 60vegthyhp.fsf@dba2.int.libertyrms.com обсуждение исходный текст |
| Ответ на | Re: TOASTing smaller things (Andreas Pflug <pgadmin@pse-consulting.de>) |
| Ответы |
Re: TOASTing smaller things
|
| Список | pgsql-hackers |
llonergan@greenplum.com ("Luke Lonergan") writes:
> Andreas,
>
> On 3/22/07 9:40 AM, "Andreas Pflug" <pgadmin@pse-consulting.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.
Hmm. Are you trying to do something sort of like CStore?
http://db.csail.mit.edu/projects/cstore/
That seems to have some relevant ideas...
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/finances.html
Where do you *not* want to go today? "Confutatis maledictis, flammis
acribus addictis" (<http://www.hex.net/~cbbrowne/msprobs.html>
В списке pgsql-hackers по дате отправления: