From: | decibel <decibel(at)decibel(dot)org> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org mailing list postgres" <pgsql-general(at)postgresql(dot)org> |
Subject: | What happens when syslog gets blocked? |
Date: | 2009-08-06 16:59:57 |
Message-ID: | 80EF22B4-8A9E-40B3-8C4B-11C2F50A1D3C@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
We recently had a problem with a database where the /var filesystem
got corrupted. This appears to have seriously impacted the ability of
STDERR from Postgres to get put out to disk, which ended up blocking
backends.
Because of this we want to switch from using STDERR to using syslog,
but I'm not sure if syslog() can end up blocking or not. I know that
(by default) syslog uses UDP when logging to an external syslog, but
what happens if you're using the local syslog? Is it still UDP or
some other mechanism that could potentially block the backends?
Also, I think we should either warn users about STDERR (and
presumably the CVS logging) or change things so that something that
breaks logging doesn't block backends.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-06 18:43:32 | Re: What happens when syslog gets blocked? |
Previous Message | Peter Eisentraut | 2009-08-06 10:28:01 | Re: [COMMITTERS] pgsql: Use DocBook XSL stylesheets for man page building This switches |
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-08-06 17:06:42 | Re: Clients disconnect but query still runs |
Previous Message | Josh Trutwin | 2009-08-06 16:53:16 | Empty Updates, ON UPDATE triggers and Rules |