Re: pgaudit - an auditing extension for PostgreSQL

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: pgaudit - an auditing extension for PostgreSQL
Дата
Msg-id 20140729130838.GB2791@momjian.us
обсуждение исходный текст
Ответ на Re: pgaudit - an auditing extension for PostgreSQL  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: pgaudit - an auditing extension for PostgreSQL  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On Thu, Jun 26, 2014 at 09:59:59AM -0400, Stephen Frost wrote:
> Simon,
> 
> * Simon Riggs (simon@2ndQuadrant.com) wrote:
> > "Which tables are audited" would be available via the reloptions
> > field. 
> 
> RLS could be implemented through reloptions too.  Would it be useful to
> some people?  Likely.  Would it satisfy the users who, today, are
> actually asking for that feature?  No (or at least, not the ones that
> I've talked with).  We could expand quite a few things to work through
> reloptions but I don't see it as a particularly good design for complex
> subsystems, of which auditing is absolutely one of those.

I saw many mentions of pg_upgrade in this old thread.  I think the focus
should be in pg_dump, which is where the SQL syntax or custom reloptions
would be dumped and restored.  pg_upgrade will just use that
functionality.  In summary, I don't think there is anything
pg_upgrade-specific here, but rather the issue of how this information will
be dumped and restored, regardless of whether a major upgrade is taking
place.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Production block comparison facility
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: pgaudit - an auditing extension for PostgreSQL