| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | A J <s5aly(at)yahoo(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Confused by 'timing' results |
| Date: | 2010-09-02 19:15:35 |
| Message-ID: | AANLkTimJ+ow5omzsQ=r1TZp1kW8nx6QiVDPifhNvfXXR@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Sep 2, 2010 at 1:02 PM, A J <s5aly(at)yahoo(dot)com> wrote:
> Do you think changing log_destination to syslog may make a difference (Kevin
> mentioned even this timing is not totally immune from network effects but if
> possible to measure should be very close to the query time) ?
At least try putting it on a different drive if you can, or remote
logging if you can't plug another drive in to the machine to put the
logs on.
--
To understand recursion, one must first understand recursion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-09-02 19:17:42 | Re: Confused by 'timing' results |
| Previous Message | Kevin Grittner | 2010-09-02 19:09:39 | Re: Confused by 'timing' results |