| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: count * performance issue |
| Date: | 2008-03-08 06:13:12 |
| Message-ID: | 16334.1204956792@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> I know when I'm playing with pgbench the primary key index on the big
> accounts table is 1/7 the size of the table, and when using that table
> heavily shared_buffers ends up being mostly filled with that index. The
> usage counts are so high on the index blocks relative to any section of
> the table itself that they're very sticky in memory. And that's toy data;
> on some of the webapps people want these accurate counts for the ratio of
> index size to table data is even more exaggerated (think web forum).
Remember that our TOAST mechanism acts to limit the width of the
main-table row.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | paul rivers | 2008-03-08 07:11:19 | Re: count * performance issue |
| Previous Message | Mark Mielke | 2008-03-08 05:31:42 | Re: count * performance issue |