Stuart Bishop wrote:
It might be possible to trick csvlog to log to a static filename, and
perhaps substituting that with a named pipe might work (under unix at
least).
As someone who did a bit of the work on the CSV log feature, I'll tell
you the way you have to note the log filename, accoun
Stuart Bishop wrote:
-- Start of PGP signed section.
>
>
> On Wed, Mar 10, 2010 at 8:51 AM, Bruce Momjian wrote:
> > Greg Sabino Mullane wrote:
> >> Bruce replied:
> >> ...
> >> >> This means that, even using syslog as a destination, it's not possible
> >> >> for
> >> >> me to filter statements
On Wed, Mar 10, 2010 at 10:55 AM, Ben Chobot wrote:
> On Mar 10, 2010, at 12:15 AM, Stuart Bishop wrote:
>
> > syslog doesn't give you easily machine readable output. I'm not sure how
> syslog implementations handle high load (our sysadmins won't use it, so I
> haven't investigated this further).
On Mar 10, 2010, at 12:15 AM, Stuart Bishop wrote:
> syslog doesn't give you easily machine readable output. I'm not sure how
> syslog implementations handle high load (our sysadmins won't use it, so I
> haven't investigated this further).
Have you looked into syslog-ng? I believe it does just
2010/3/10 Stuart Bishop :
>
>
> On Wed, Mar 10, 2010 at 8:51 AM, Bruce Momjian wrote:
>>
>> Greg Sabino Mullane wrote:
>>>
>>> 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-te
On Wed, Mar 10, 2010 at 8:51 AM, Bruce Momjian wrote:
Greg Sabino Mullane wrote:
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, performan
Greg Sabino Mullane wrote:
> 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
-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.
>
G Dutton wrote:
> Hello all,
>
> I've seen some rather tangential postings about means of filtering log
> messages, but none quite match up to (what I believe to be) my
> requirement, so here goes:
>
> As a means of auditing our database server, I would like to use the
> PostgreSQL 'log_statement
