| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: some requests on auditing |
| Date: | 2016-08-31 14:00:02 |
| Message-ID: | 26393985-1958-24a5-1d4b-063ff0796eeb@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-31 14:01:50 | Re: pg_sequence catalog |
| Previous Message | Greg Stark | 2016-08-31 13:46:30 | Re: autonomous transactions |