Re: log_statement and syslog severity

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Bruce replied:
...
>> This means that, even using syslog as a destination, it's not possible for
>> me to filter statements without some sort of log-text parsing, which I'd
>> prefer to avoid on effort, performance and data-integrity grounds.

> Our logging system is very flexible, but not work-free on the user end.
> I don't see us changing things in that area.

Bruce, that's a little harsh, I think the original poster has a legitimate
request. Personally, I'd love to be able to split the logs on various things,
the most important to me being durations and per-database. I looked at the
code about a year ago to see how hard this would be and found it non-trivial
(for me), as we're really assuming hard things go to a single filehandle.
It's definitely an area for improvement, and should be a TODO if not already.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 201003091022
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkuWZ88ACgkQvJuQZxSWSsgVvgCfaWaOqcJEzfKBQiN5ttvU/EMB
lVYAn1Ud1AccynciWGvhfqIInNZK1+DZ
=qEnX
-----END PGP SIGNATURE-----