From: | Andy Colson <andy(at)squeakycode(dot)net> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Jayadevan M <Jayadevan(dot)Maymala(at)ibsplc(dot)com> |
Subject: | Re: Getting value of bind variables |
Date: | 2011-08-19 14:04:20 |
Message-ID: | 4E4E6D64.2090808@squeakycode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/19/2011 9:01 AM, Adrian Klaver wrote:
> On Friday, August 19, 2011 6:55:39 am Andy Colson wrote:
>>> As of now, I am trying with logging level set to debug5 in
>>> postgresql.conf for all logging options. But what is the 'correct'
>>> approach?
>>>
>>> Regards,
>>> Jayadevan
>>
>> Not sure what the exact setting is, try:
>>
>> log_statement = 'all'
>>
>> I've never set the log_min_messages or log_min_error_statement, and I'm
>> pretty sure I've seen values in my logs.
>
> If I remember correctly this is version specific, though I cannot remember what
> version the actual variables where made visible:(
>
Ah, yeah, you are probably right.
I can confirm in PG 9, with just
>> log_statement = 'all'
I see things like:
DETAIL: parameters: $1 = '%oak%'
in my log.
-Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-08-19 14:05:37 | Re: Dump a database excluding one table DATA? |
Previous Message | Tom Lane | 2011-08-19 14:04:00 | Re: Getting value of bind variables |