| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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 13:14:07 |
| Message-ID: | Pine.LNX.4.44.0310051511340.2745-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane writes:
> Sure it can. You're essentially arguing that DBAs are too dumb to match
> up matching query and duration log outputs. I don't buy that. I think
> they'll be analyzing their logs with little Perl scripts anyway, and
> that consistency of log output format will be worth more to those
> scripts than sometimes having related items all on one log line.
When you're dealing with a large installation, these little Perl scripts
become difficult. I've just had to deal with a similar issue with a
popular MTA which spreads the relevant log information over several lines.
If you're generating 500 MB of log output a day, it becomes a problem.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-10-05 13:16:34 | Re: fix log_min_duration_statement logic error |
| Previous Message | Peter Eisentraut | 2003-10-05 12:49:48 | Translators wanted for PostgreSQL |