| From: | Chris Browne <cbbrowne(at)acm(dot)org> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Clustered tables improves perfs ? |
| Date: | 2007-09-13 14:49:57 |
| Message-ID: | 608x7azkkq.fsf@dba2.int.libertyrms.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
pcastet(at)agematis(dot)com (Patrice Castet) writes:
> I wonder if clustering a table improves perfs somehow ?
> Any example/ideas about that ?
> ref : http://www.postgresql.org/docs/8.2/interactive/sql-cluster.html
Sometimes.
1. It compacts the table, which may be of value, particularly if the
table is not seeing heavy UPDATE/DELETE traffic. VACUUM and VACUUM
FULL do somewhat similar things; if you are using VACUUM frequently
enough, this is not likely to have a material effect.
2. It transforms the contents of the table into some specified order,
which will improve efficiency for any queries that use that specific
ordering.
--
output = reverse("moc.enworbbc" "@" "enworbbc")
http://linuxdatabases.info/info/emacs.html
"You can swear at the keyboard and it won't be offended. It was going
to treat you badly anyway" -- Arthur Norman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Nicholson | 2007-09-13 15:03:22 | Re: Long Running Commits - Not Checkpoints |
| Previous Message | Scott Marlowe | 2007-09-13 14:29:34 | Re: [Again] Postgres performance problem |