From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rbt(at)rbt(dot)ca>, 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-07 16:56:35 |
Message-ID: | 200310071656.h97GuZk20298@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Another idea if you like consistency would be:
> >
> > LOG: duration: 4.056 ms query: select * \nfrom pg_language;
>
> Speaking of consistency...
>
> Imagine someone always having log_statement on and doing some sort of
> aggregate query counting, say like grep '^LOG: query:' | wc -l. Now that
> someone (or maybe the admin on the night shift, to make it more dramatic)
> also turns on log_min_statement_duration (or whatever it's spelled), say
> to find the slowest queries: grep '^LOG: duration:' | sort -xyz | head
> -10. In order to guarantee the consistency of both results, you'd have to
> log each query twice in this case.
I guess.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Sugawara | 2003-10-07 23:34:01 | Spanish translations of pg_dump and pg_resetxlog |
Previous Message | Bruce Momjian | 2003-10-07 16:55:44 | Re: fix log_min_duration_statement logic error |