| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | decibel <decibel(at)decibel(dot)org> |
| Cc: | "pgsql-general(at)postgresql(dot)org mailing list postgres" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: What happens when syslog gets blocked? |
| Date: | 2009-08-06 18:43:32 |
| Message-ID: | 27713.1249584212@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
decibel <decibel(at)decibel(dot)org> writes:
> 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.
syslog (at least in the implementations I'm familiar with) has the
opposite problem: when the going gets tough, it starts losing messages.
I do not think you'll really be making your life better by switching.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2009-08-06 19:00:37 | Re: What happens when syslog gets blocked? |
| Previous Message | decibel | 2009-08-06 16:59:57 | What happens when syslog gets blocked? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david.schruth | 2009-08-06 18:48:33 | Re: JOIN a UNION |
| Previous Message | Merlin Moncure | 2009-08-06 18:35:29 | Re: Empty Updates, ON UPDATE triggers and Rules |