| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Subject: | Re: PostgreSQL Audit Extension |
| Date: | 2016-02-19 16:02:33 |
| Message-ID: | 20160219160233.GC30338@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 19, 2016 at 12:54:17PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Understood. My point is that there is a short list of read events, and
> > many DDL events. We have already hesitated to record DDL changes for
> > logical replication because of the code size, maintenance overhead, and
> > testing required.
>
> DDL is already captured using the event triggers mechanism (which is
> what it was invented for in the first place). The only thing we don't
> have is a hardcoded mechanism to transform it from C struct format to
> SQL language.
Right, which is I think were the maintenance/testing overhead will come
from, which we are trying to avoid. Having logical replication and
auditing share that burden would be a win.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2016-02-19 16:10:03 | Re: 9.5 new setting "cluster name" and logging |
| Previous Message | Alvaro Herrera | 2016-02-19 15:54:17 | Re: PostgreSQL Audit Extension |