Re: Need query parameter in logs
| От | Tsirkin Evgeny |
|---|---|
| Тема | Re: Need query parameter in logs |
| Дата | |
| Msg-id | dd5da9d90602130059r77725da6re95a1cdb737daf93@mail.gmail.com обсуждение исходный текст |
| Ответ на | Need query parameter in logs (Robert Perry <rlperry@lodestonetechnologies.com>) |
| Список | pgsql-admin |
Well I am not a guru ,but maybe you can add
raise notice
to your game_state_set_disqualified ?
raise notice
to your game_state_set_disqualified ?
On 2/9/06, Robert Perry < rlperry@lodestonetechnologies.com> wrote:
I am trying to help debug a application that is deployed in the
field. I suspect that it is sending some unexpected values to some
stored procs, but the logs look very much like:
Feb 9 14:29:26 localhost postgres[3138]: [122-1] LOG: statement:
Select * from game_state_set_disqualified( $1, $2, $3, $4 )
How can I find out what $1, $2, $3, $4 are short of recompiling the C
++ client code?
Thanks
Robert Perry
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
В списке pgsql-admin по дате отправления: