We'd like to attempt some log replay to simulate real loads, but
in 8.1.2, it appears the formal parameters are logged ('$')
instead of the actuals for prepared queries, e.g.:

EXECUTE <unnamed> [PREPARE: UPDATE sessions SET a_session = $1
WHERE id = $2]

Thoughts on making this a to-do item?

Ed

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On 7/15/06, Ed L. <pgsql@bluepolka.net> wrote:
>
> We'd like to attempt some log replay to simulate real loads, but
> in 8.1.2, it appears the formal parameters are logged ('$')
> instead of the actuals for prepared queries, e.g.:
>
> EXECUTE <unnamed> [PREPARE: UPDATE sessions SET a_session = $1
> WHERE id = $2]
>
> Thoughts on making this a to-do item?
>
> Ed
>

i think this is the one you are requesting, it's a TODO item already:

o Allow protocol-level BIND parameter values to be logged

--
Atentamente,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Ed L. wrote:
>
> We'd like to attempt some log replay to simulate real loads, but
> in 8.1.2, it appears the formal parameters are logged ('$')
> instead of the actuals for prepared queries, e.g.:
>
> EXECUTE <unnamed> [PREPARE: UPDATE sessions SET a_session = $1
> WHERE id = $2]
>
> Thoughts on making this a to-do item?

It is already a TODO item:

* Allow protocol-level BIND parameter values to be logged

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq