From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TOAST code ignores freespace (was Tweak TOAST code) |
Date: | 2010-05-04 08:14:25 |
Message-ID: | 1272960865.4535.325.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Mon, 2010-05-03 at 23:36 -0400, Jan Wieck wrote:
> Suppose we had something similar to the NULL value bitmap, specifying
> plain or compressed values (not TOAST references), that are moved to a
> shadow tuple inside the toast table. Suppose further we had some
> statistics about how often attributes appear in a qualification (i.e.
> end up in a scan key or scan filter or other parts of the qual
> expression list). Not sure, maybe we even want to know how often or
> seldom an attribute is heap_getattr()'d at all. Those don't need to be
> accurate counts. Small random samples will probably do. ANALYZE could
> evaluate those statistics and adjust the "shadow" storage settings per
> attribute accordingly.
>
> I can imagine many applications, where this would shrink the main
> tuples to almost nothing at all.
Automatic vertical partitioning. Like it.
TODO item for further detailed research.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | User Mkz | 2010-05-04 10:33:12 | pgbouncer - pgbouncer: Forgot to change second listen() call also to |
Previous Message | Jan Wieck | 2010-05-04 03:36:24 | Re: TOAST code ignores freespace (was Tweak TOAST code) |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-05-04 08:37:17 | Re: max_standby_delay considered harmful |
Previous Message | Simon Riggs | 2010-05-04 08:02:09 | Pause/Resume feature for Hot Standby |