| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | SpaceBallOne <space_ball_one(at)hotmail(dot)com> |
| Cc: | John A Meinel <john(at)arbash-meinel(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Can anyone explain this: duplicate dbs. |
| Date: | 2005-05-25 03:00:54 |
| Message-ID: | 4293EA66.3070401@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> Would CLUSTER / REINDEX still have an effect if our queries were done
> via sequential scan?
SELECTS don't write to the database, so they have no effect at all on
vacuuming/analyzing. You only need to worry about that with writes.
> This is a old database (as in built by me when i
> was just starting to learn unix / postgres) so the database design is
> pretty horrible (little normalisation, no indexes).
No indexes? Bloody hell :D
Use EXPLAIN ANALYZE SELECT ... ; on all of your selects to see where
they are slow and where you can add indexes...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-25 03:01:28 | Re: Can anyone explain this: duplicate dbs. |
| Previous Message | John A Meinel | 2005-05-25 03:00:34 | Re: Can anyone explain this: duplicate dbs. |