From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
Cc: | "Jan Wieck" <JanWieck(at)Yahoo(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Chris Browne" <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TOASTing smaller things |
Date: | 2007-04-10 14:30:38 |
Message-ID: | C240ED9E.2C04B%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Bruce,
How about these:
- Allow specification of TOAST size threshold in bytes on a per column basis
- Enable storage of columns in separate TOAST tables
- Enable use of multi-row compression method(s) for TOAST tables
- Luke
On 3/26/07 5:39 PM, "Bruce Momjian" <bruce(at)momjian(dot)us> wrote:
> Luke Lonergan wrote:
>> I advocate the following:
>>
>> - Enable specification of TOAST policy on a per column basis
>>
>> As a first step, then:
>>
>> - Enable vertical partitioning of tables using per-column specification of
>> storage policy.
>>
>
> How are these different from ALTER TABLE SET STORAGE? They need to be
> more specific.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-04-10 14:32:38 | Re: \da doesn't show result type |
Previous Message | Nikolay Samokhvalov | 2007-04-10 14:25:16 | Re: "select ('{}'::text[])[1]" returns NULL -- is it correct? |