| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | ohp(at)pyrenet(dot)fr |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: fix log_min_duration_statement logic error |
| Date: | 2003-10-05 17:05:32 |
| Message-ID: | 1065373485.23288.173.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> > That was true already with log_statement and log_duration as separate
> > operations. People use log_pid to deal with it.
> Sorry to jump in... the log_pid is NOT ENOUGH where you have more than
> 30000 connections a day (witch is my case)
log_pid isn't enough, but log_pid + log_connections certainly is.
log_connections tells you when a new connection was made, so guessing
isn't required.
> There has been discussion as to have 1 Log file/database where are we on
> that? Is it dead?
Well, this wouldn't help either unless you happen to have several not so
active databases that makes for a busy system.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Serguei Mokhov | 2003-10-05 17:09:24 | Russian NLS update: pg_dump, libpq, psql |
| Previous Message | ohp | 2003-10-05 16:39:10 | Re: fix log_min_duration_statement logic error |