Not quite the same - timestamps and pids have known formats, while db names are almost arbitrary. I know including spaces in names is horrible to my *nix way of thinking, but others might not have my prejudices. (interesting question - what characters are NOT allowed in a database name?).

BTW, we're talking about 5 extra chars per line here. I know it adds up, but these days disk space is cheap and plentiful - for a million log lines we're still only talking 5Mb (says he whose first machine had a whopping 20Mb of disk space, and who paid hundreds of (aussie) dollars for the extra 10 Mb.)

Syslog puts [] around pids, and typically has a lot of redundancy.

I'm prepared to be guided by concensus, though.

cheers

andrew


Tom Lane wrote:


Andrew Dunstan <[EMAIL PROTECTED]> writes:


The dbname patch is now done. If nobody objects to the format ("[db:yourdbname]") I'll submit it - I did it that way to make it fairly easy to split a log file based on it, although you would have to be careful with multiline log entries such as query strings.



I'd tend to just put the dbname in a known column, and not bother with the decoration --- decoration adds up fast when it's on every log line, and I don't think it helps make the log more parseable. Compare what we do with timestamps and pids.

regards, tom lane






---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly

Reply via email to