Oh, interesting. I didn't realize you could change that on the fly. That's helpful.
So, I tried turning statement logging on and that didn't give me any more detail. I think that is because the query I want to inspect is generating an error (which I failed to mention in my original question).
ERROR: invalid input syntax for type double precision: "A"
STATEMENT: insert into x (a,b,c,d,e,f) VALUES ($1,$2,$3,$4,$5,$6)
columns c, d, e are all double precision, so I'm not sure which one has the bad data. If I knew what values $1 and $2 were, I could pinpoint the record that is generating the error.
So, my revised question: is there any way to inspect the values from a prepared statement when the query contains an error? Or some combination of logging settings that would give me that detail?
Thanks!
On 05/02/2016 11:00 AM, Natalie Wenz wrote:Is it possible to turn that on without interrupting current traffic?
Yes with a HUP or reload.JD
On May 2, 2016, at 12:54 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
On 05/02/2016 10:51 AM, Natalie Wenz wrote:
Is there any way for an administrator to view the values of a prepared statement that is currently executing?
statement logging will do it.
Thanks!
Natalie
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
-- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564PostgreSQL Centered full stack support, consulting and development.Everyone appreciates your honesty, until you are honest with them.