From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Logging Parameter Values |
Date: | 2008-06-19 15:05:25 |
Message-ID: | 12707.1213887925@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Volkan YAZICI <yazicivo(at)ttmail(dot)com> writes:
> 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);
> 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);
Hmm, we're not on the same page here. I thought you were talking about
protocol-level parameters. In the above example, the parameter values
are shown in the EXECUTE statement, so what else do you need?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-06-19 15:18:42 | Re: Logging Parameter Values |
Previous Message | Volkan YAZICI | 2008-06-19 14:54:32 | Re: Logging Parameter Values |