| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Ian Barwick <ian(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgaudit - an auditing extension for PostgreSQL |
| Date: | 2014-06-24 17:44:07 |
| Message-ID: | 20140624174407.GS16098@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Fujii Masao (masao(dot)fujii(at)gmail(dot)com) wrote:
> I'm not sure if this is good idea because this basically means that master
> and every standbys must have the same audit settings and a user cannot
> set what standby logs in standby side. Of course I guess that the audit
> settings in standby would be similar to that in master generally, but I'm
> not sure if that's always true.
The main difference would be that the standby wouldn't be logging
anything about data changing.. but that's to be expected.
Certainly when auditing of select queries and similar actions are done
to satisfy government or industry compliance requirements, it's about
"who reads the data", regardless of where that data is..
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Muraviov | 2014-06-24 17:45:18 | Re: wrapping in extended mode doesn't work well with default pager |
| Previous Message | Kevin Grittner | 2014-06-24 17:43:18 | Re: idle_in_transaction_timeout |