From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: some requests on auditing |
Date: | 2016-08-31 14:41:48 |
Message-ID: | CAFj8pRC=uW=LYELPrdn=D0XXeLzboJ=JyyjFEE99RwJkzrqRRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2016-08-31 16:00 GMT+02:00 David Steele <david(at)pgmasters(dot)net>:
> On 8/31/16 9:39 AM, David Steele wrote:
>
>> On 8/30/16 10:12 AM, Pavel Stehule wrote:
>>
>
> #3 is not likely without changes to logging in Postgres. However, there
>> are plenty of tools for log analysis (e.g. ELK) that might help and a
>> Postgres extension that allows log messages to be directed elsewhere
>> (can't remember the name but Gabrielle or Simon would know).
>>
>
> Here's the extension I was thinking of:
>
> https://github.com/2ndquadrant-it/redislog
>
> This one is more general purpose:
>
> https://github.com/mpihlak/pg_logforward
>
many thanks you for these informations - I'll check it.
Regards
Pavel
> --
> -David
> david(at)pgmasters(dot)net
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2016-08-31 14:47:18 | Optimizing aggregates |
Previous Message | Petr Jelinek | 2016-08-31 14:40:25 | Re: pg_sequence catalog |