From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: logging stuff |
Date: | 2003-08-05 17:37:18 |
Message-ID: | 3F2FEB4E.5010901@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
It's more work for a very small cosmetic benefit, ISTM. Setting up
atomic GUC variables is trivially easy, I'm happy to say. Not that I
can't write a simple parser, but why bother for something so tiny?
Also, would we be saying (or implying) that the order given on the line
would affect the output? If so, that could make LOTS more work, again
for very small benefit, I think.
(Yes, of course this is for 7.5).
cheers
andrew
Bruce Momjian wrote:
>I think we need a more general variable that can take several values,
>separated by commas, like:
>
> log_line: dbname,user
>
>or something like that.
>
>In fact, looking at the postgresql.conf file, I see only two setting
>that print on every line: log_pid and log_timestamp. Perhaps those two
>should be merged into log_line.
>
>Of course, this is all for 7.5.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2003-08-05 17:40:17 | Re: Release changes |
Previous Message | Joe Conway | 2003-08-05 17:08:04 | Re: Release changes |