| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
| Cc: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres server output logfile |
| Date: | 2003-02-04 13:01:20 |
| Message-ID: | 20030204130120.GB3239@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 04, 2003 at 08:39:03 +1100,
Giles Lean <giles(at)nemeton(dot)com(dot)au> wrote:
>
> Jean-Luc Lachance <jllachan(at)nsd(dot)ca> writes:
>
> > He is my very simple solution:
>
> One of the constraints on the code that I wrote was that it try to be
> robust. Having the database go down because the log writing program
> exited due to a transiently full filesystem was thought to be
> undesirable -- see Tom Lane's comments in the archives.
multilog will block instead of exit when a file system fills up. That
may or may not be better for you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fernando Schapachnik | 2003-02-04 13:18:37 | Re: Kernel Error |
| Previous Message | Bruno Wolff III | 2003-02-04 12:59:54 | Re: Dealing with complex queries |