| From: | bricklen <bricklen(at)gmail(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Bjørn T Johansen <btj(at)havleik(dot)no>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Analyze tool? |
| Date: | 2010-10-01 14:46:08 |
| Message-ID: | AANLkTi=8uWZQUXZTEgyoGcnJCupYUe1Cv3Pm-LOMMNC6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2010/10/1 Thom Brown <thom(at)linux(dot)com>:
> But to find out what indexes you'll need, getting used to reading
> query plans will help as it will show you more than just where
> sequentials scans are taking place. It will also show you what the
> planner believes a query will cost compared to how much it actually
> costs, which can provide insight into tables which require vacuuming,
> indexes which might need clustering, or table stats which require
> modifying to match you data.
A couple related tools to help with explain plans are the query
analyzer in pgAdmin
(http://www.pgadmin.org/images/screenshots/pgadmin3_macosx.png), and
online at http://explain.depesz.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2010-10-01 14:59:17 | Re: Copying a column into a temp. table |
| Previous Message | Alexander Farber | 2010-10-01 14:40:09 | How to restore "postgres" database? |
