Thanks, I did check log_min_error_statement; no additional information. I also tried dialing
log_min_duration_statementto 0, same result. Both things *did* show the values used for other, successful, queries that
wereusing prepared statements. But in the case of the query that was triggering the error, none of those options logged
thevalues used in the prepared statement. Is that expected behavior?
We're running postgres 9.3.11 on that server.
Thanks again,
Natalie
> On May 2, 2016, at 2:13 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
>
> On 05/02/2016 11:41 AM, Natalie Wenz wrote:
>> Oh, interesting. I didn't realize you could change that on the fly.
>> That's helpful.
>
>>
>> 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?
>>
>
> What version are you running? Also check log_min_error_statement
>
> Sincerely,
>
> JD
>
> --
> 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.