| From: | Ants Aasma <ants(at)cybertec(dot)at> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Guide to Posting Slow Query Questions |
| Date: | 2012-09-13 06:40:11 |
| Message-ID: | CA+CSw_sxnsjzrfuUYxfF3SzO3cvXma8kSUPcoQjiEjmRoWKfkw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Sep 12, 2012 at 7:00 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Regarding the wiki page on reporting slow queries:
> We currently recommend EXPLAIN ANALYZE over just EXPLAIN. Should we
> recommend EXPLAIN (ANALYZE, BUFFERS) instead? I know I very often
> wish I could see that data. I don't think turning buffer accounting
> on adds much cost over a mere ANALYZE.
Given the amount of version 8 installs out there the recommendation
should be qualified with version >9.0. Otherwise a strong +1
> Also, an additional thing that would be nice for people to report is
> whether long running queries are CPU bound or IO bound. Should we add
> that recommendation with links to how to do that in a couple OS, say,
> Linux and Windows. If so, does anyone know of good links that explain
> it for those OS?
I don't have any links for OS level monitoring, but with version 9.2
track_io_timing would do the job.
Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Martin | 2012-09-13 09:05:26 | Re: Planner selects different execution plans depending on limit |
| Previous Message | Jeff Janes | 2012-09-12 16:00:50 | Guide to Posting Slow Query Questions |