From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Ants Aasma <ants(at)cybertec(dot)at> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Guide to Posting Slow Query Questions |
Date: | 2012-10-16 17:38:34 |
Message-ID: | CAMkU=1wG48HGRNZ2Qn2f1wPCd9KB5fbx-SjQ6ZQwynbShKbaLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sun, Oct 7, 2012 at 7:43 AM, Ants Aasma <ants(at)cybertec(dot)at> wrote:
> On Wed, Sep 26, 2012 at 11:11 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>> On Wed, Sep 12, 2012 at 11:40 PM, Ants Aasma <ants(at)cybertec(dot)at> wrote:
>>> 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?
>
> I added a line suggesting that 9.2 users turn it on via SET
> track_io_timing TO on;
That was easy. I thought there was more to it because I didn't get
any IO timing output when I tried it. But that was just because there
was nothing to output, as all data was in shared_buffers by the time I
turned the timing on.
Thanks,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-10-16 19:23:34 | Re: limit order by performance issue |
Previous Message | ktm@rice.edu | 2012-10-16 12:52:49 | Re: Support Create package |