Thread: How compare current_setting(..) ?

Hi there,

I'd like to check that my log_line_prefix is set to '%t'.
I suppose I can check it with the following statement:   SELECT current_setting( 'log_line_prefix' )   WHERE
current_setting('log_line_prefix' ) != '%t'
 

But it returns every time a row, with '%t', even when log_line_prefix is set 
to '%t'.
What's wrong ?

TIA,
Sabin 

On Thu, Feb 22, 2007 at 12:25:42PM +0200, Sabin Coanda wrote:
> I'd like to check that my log_line_prefix is set to '%t'.
> I suppose I can check it with the following statement:
>     SELECT current_setting( 'log_line_prefix' )
>     WHERE current_setting( 'log_line_prefix' ) != '%t'
> 
> But it returns every time a row, with '%t', even when log_line_prefix is set 
> to '%t'.
> What's wrong ?

Works here.  Might log_line_prefix have leading or trailing spaces?
What does the following return?

SELECT '<' || current_setting('log_line_prefix') || '>',      length(current_setting('log_line_prefix'));

-- 
Michael Fuhr

Sorry, it was my fault. The setting was '%t' and a space. I fixed it and it 
works well.
Many thanks !

"Michael Fuhr" <mike@fuhr.org> wrote in message 
news:20070222110353.GA7197@winnie.fuhr.org...
> On Thu, Feb 22, 2007 at 12:25:42PM +0200, Sabin Coanda wrote:
>> I'd like to check that my log_line_prefix is set to '%t'.
>> I suppose I can check it with the following statement:
>>     SELECT current_setting( 'log_line_prefix' )
>>     WHERE current_setting( 'log_line_prefix' ) != '%t'
>>
>> But it returns every time a row, with '%t', even when log_line_prefix is 
>> set
>> to '%t'.
>> What's wrong ?
>
> Works here.  Might log_line_prefix have leading or trailing spaces?
> What does the following return?
>
> SELECT '<' || current_setting('log_line_prefix') || '>',
>       length(current_setting('log_line_prefix'));
>
> -- 
> Michael Fuhr
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>
>