| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Natalie Wenz <nataliewenz(at)ebureau(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Inspect values of prepared statements |
| Date: | 2016-05-02 21:17:29 |
| Message-ID: | 5727C3E9.7040103@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 05/02/2016 02:10 PM, Natalie Wenz wrote:
> Thanks, I did check log_min_error_statement; no additional information. I also tried dialing log_min_duration_statement to 0, same result. Both things *did* show the values used for other, successful, queries that were using prepared statements. But in the case of the query that was triggering the error, none of those options logged the values used in the prepared statement. Is that expected behavior?
>
> We're running postgres 9.3.11 on that server.
Can you attach your postgresql.conf?
--
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-02 21:40:59 | Re: Inspect values of prepared statements |
| Previous Message | Natalie Wenz | 2016-05-02 21:10:10 | Re: Inspect values of prepared statements |