Re: Guide to Posting Slow Query Questions

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: Guide to Posting Slow Query Questions
Дата
Msg-id CAMkU=1xekNuoVp5oQSdTdaBY9g0nOLmM7D8Q97CneM4kp5Pm6A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Guide to Posting Slow Query Questions  (Ants Aasma <ants@cybertec.at>)
Ответы Re: Guide to Posting Slow Query Questions
Список pgsql-performance
On Wed, Sep 12, 2012 at 11:40 PM, Ants Aasma <ants@cybertec.at> wrote:
> On Wed, Sep 12, 2012 at 7:00 PM, Jeff Janes <jeff.janes@gmail.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

Edit made.

>
>> 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.

I don't know how to advice people on how to use this to obtain
information on a specific query.  Would someone else like to take a
stab at explaining that?

Thanks,

Jeff


В списке pgsql-performance по дате отправления:

Предыдущее
От: Shaun Thomas
Дата:
Сообщение: Re: Inaccurate Explain Cost
Следующее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: Inaccurate Explain Cost