From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Michael Nacos <m(dot)nacos(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ibrahim Harrani <ibrahim(dot)harrani(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: postgresql and syslog |
Date: | 2009-08-07 19:56:50 |
Message-ID: | 20090807195650.GB5290@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Michael Nacos escribió:
> I would be very surprised if logging had a significant overhead any method
> you choose. there's probably something very wrong with your setup if this
> is the case.
Either something very wrong, or the load is extremely high. In the
latter case perhaps it would make sense to ship syslog to a remote
machine. Since it uses UDP sockets, it wouldn't block when overloaded
but rather lose messages (besides, it means it has low overhead).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Kupershmidt | 2009-08-07 20:17:12 | PG-related ACM Article: "The Pathologies of Big Data" |
Previous Message | Michael Nacos | 2009-08-07 13:06:34 | Re: postgresql and syslog |