From: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
---|---|
To: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres server output logfile |
Date: | 2003-02-03 21:39:03 |
Message-ID: | 2595.1044308343@nemeton.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
> if ( output == NULL)
> {
> fprintf( stderr, "%s: cannot write to file: %s", argv[ 0], argv[
> 1]);
> exit( 2);
> }
The Apache rotatelogs program is similar, or was when I looked at it
last. Perhaps they've worked on it recently. (Perhaps I should offer
some improvements ... in my copious spare time. :-)
Regards,
Giles
From | Date | Subject | |
---|---|---|---|
Next Message | Patric Bechtel | 2003-02-03 21:47:22 | Re: 335 times faster (!) [Viruschecked] |
Previous Message | Francisco Reyes | 2003-02-03 21:32:10 | Dealing with complex queries |