| From: | Lamar Owen <lowen(at)pari(dot)edu> |
|---|---|
| To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
| Cc: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Log rotation |
| Date: | 2004-03-13 18:13:21 |
| Message-ID: | 200403131313.21280.lowen@pari.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Saturday 13 March 2004 01:00 pm, Fernando Nasser wrote:
> There are some applicatons which run in servers with very strict
> response times and any syscall, network packet that can be saved counts.
Ok, what about pipe overhead? If we're gong to split hairs, let's split all
of them. The design of the pipeline in this logrotator filter will have to
be such that minimal overhead occurs, because, at the real-time level, every
concurrent process also counts.
> The number of generated messgaes.
> Maybe that is an area that can be worked on, i.e. reducing log
> verbosity. Is 7.4.x much better than 7.3.x in that respect?
There are several levels documented in postgresql.conf. Try the terse level
and see what happens.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-03-13 19:12:58 | Re: Log rotation |
| Previous Message | Lamar Owen | 2004-03-13 18:09:46 | Re: Log rotation |