Re: [PATCHES] log_line_info - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCHES] log_line_info
Date
Msg-id 200402290431.i1T4Vrs27431@candle.pha.pa.us
Whole thread Raw
Responses Re: [PATCHES] log_line_info  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan wrote:
> >Nice.  Only two comments --- does this mean we should remove log_pid? 
> >Seems it is now duplicate functionality.  Is that the only duplication?
> >Also, I don't see any documention changes in the patch, but I assume you
> >will work on that before final.
> >
> 
> I will do docs. We could sensibly get rid of log_pid and log_timestamp 
> with my latest patch. I would also suggest getting rid of 
> log_source_port, since there really isn't any reason *not* to log the 
> source port. Do you want me to make those changes in my patch? Or I can 
> leave them for now and we can get rid of them when everyone is happy.

I agree, but let's make it a separate patch.

Oh, I think we still need log_timestamp for postmaster-generated lines,
no?  What does log_line_info output for postmaster-generated logs?

Also, should we call the option just log_line?  Is that clearer, or
log_line_prefix?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tim Larson
Date:
Subject: Re: [ADMIN] Schema comparisons
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] log_line_info