Volkan YAZICI <[EMAIL PROTECTED]> 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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
