Skip site navigation (1) Skip section navigation (2)

Re: log_line_info

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: log_line_info
Date: 2004-02-29 13:11:04
Message-ID: 4041E4E8.7000704@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches

Peter Eisentraut wrote:

>Andrew Dunstan wrote:
>  
>
>>Attached is a patch for tagging log lines produced by backends. It is
>>not quite ready for application - this is for people to look over and
>>play with.
>>
>>For my testing I used the following settings:
>>
>>log_connections = true
>>log_disconnections = true
>>log_line_info = '%T [%P] %U(at)%D(%C:%S) %I line:%L '
>>log_statement = true
>>log_hostname = true
>>log_source_port = true
>>
>>
>>Comments welcome
>>    
>>
>
>I'm wondering, why did you choose to use capital letters, when normally 
>the % codes are lower-case letters when possible?  I think lower-case 
>letters are easier to read.
>  
>

I did it to differentiate them from standard printf escapes. I don't 
feel strongly about it, though. I'm currently prepping a final patch and 
docs, so I'd be grateful for an early consensus on this.

cheers

andrew


In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2004-02-29 13:19:03
Subject: Re: log_line_info
Previous:From: Rob FieldingDate: 2004-02-29 13:08:01
Subject: Re: WAL Optimisation - configuration and usage

pgsql-patches by date

Next:From: Andrew DunstanDate: 2004-02-29 13:19:03
Subject: Re: log_line_info
Previous:From: Peter EisentrautDate: 2004-02-29 12:46:33
Subject: Re: log_line_info

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group