Thanks for your reply, Lucazeo.
> BUT: it is dangerous in production: you can fill your file system very
> fast and slow down the system.
Yes, this was my concern as well. In my current situation this may be too
risky.
>Another way is: modify the trigger and write informations you need in
>a specific table. Not an elegant solution but...
Exactly what I had in mind, but I hoped to be able to log the original
statement as well .
In that way I can simulate the problem-causing transactions exactly in a
more controlled env by running the scripts as in the log table.
Thanks any way.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/debugging-triggers-get-original-statement-tp5787181p5787212.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.