| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | A J <s5aly(at)yahoo(dot)com>, 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:25:12 |
| Message-ID: | AANLkTik_rJeM=ojEL_E9D_yZknMpvYMvRhPKbsHz16sZ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Sep 2, 2010 at 1:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> A J <s5aly(at)yahoo(dot)com> writes:
>> Do you think changing log_destination to syslog may make a difference
>
> It's worth trying alternatives anyway. It is odd that you are seeing
> such a slowdown when using the collector --- many people push very high
> log volumes through the collector without problems. What PG version is
> this exactly, and on what platform?
We push a ton through the collector (up to 10 Megs a second at peak)
with no problems. but it doesn't share a drive with the main store or
pg_xlog.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Silvio Brandani | 2010-09-03 07:33:06 | Re: out of memory error |
| Previous Message | A J | 2010-09-02 19:21:24 | Re: Confused by 'timing' results |