From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | PFC <lists(at)peufeu(dot)com> |
Cc: | Jesper Krogh <jesper(at)krogh(dot)cc>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: "Slow" query or just "Bad hardware"? |
Date: | 2008-03-27 17:54:09 |
Message-ID: | 20080327175409.GP8764@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
PFC wrote:
> Also, sometimes offine TOASTing is evil :
> Say you have a forum, you want the posts table to be CLUSTER'ed on
> (topic_id, post_id) so displaying 1 page with 30 posts on it uses 1 seek,
> not 30 seeks. But CLUSTER doesn't touch the data that has been pushed
> offline in the toast table. So, in that case, it can pay (big time
> actually) to disable toasting, store the data inline, and benefit from
> cluster.
This claim is false -- CLUSTER does process the toast table along the
main heap.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2008-03-27 19:14:49 | using like in a prepare doesnt' use the right index |
Previous Message | Luke Lonergan | 2008-03-27 17:36:55 | Re: "Slow" query or just "Bad hardware"? |