From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Logging Parameter Values |
Date: | 2008-06-19 15:18:42 |
Message-ID: | 20080619151842.GS5077@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Volkan YAZICI wrote:
> I don't want to interrupt your work, but as far as I see from logs --
> with the configurations I sent previously -- PostgreSQL doesn't log
> parameter values for queries dropped into query duration limit. (Using
> PostgreSQL 8.3.1.) Consider this test case:
>
> test# PREPARE foo (int) AS
> ] SELECT S.i * T.i
> ] FROM generate_series(1, $1) AS S(i),
> ] generate_series(1, $1) AS T(i);
>
> test# EXECUTE foo (1000);
> ...
>
> # tail -n 2 /srv/pg/pg_log/2008-06-19_141725.log
> migration_test postgres 2008-06-19 17:58:05.185 EEST LOG: duration: 2315.420 ms statement: EXECUTE foo(1000);
The parameter is on the above line, isn't it?
> migration_test postgres 2008-06-19 17:58:05.185 EEST DETAIL: prepare: PREPARE foo (int) AS SELECT S.i * T.i FROM generate_series(1, $1) AS S(i), generate_series(1, $1) AS T(i);
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2008-06-19 15:54:31 | Re: Database design: Data synchronization |
Previous Message | Tom Lane | 2008-06-19 15:05:25 | Re: Logging Parameter Values |