Re: Select Column Auditing/Logging
От
Jeff Davis
Тема
Re: Select Column Auditing/Logging
Дата
Msg-id
1248299069.23273.18.camel@monkey-cat.sm.truviso.com
Ответ на
Re: Select Column Auditing/Logging (Jeff Davis)
Список
Дерево обсуждения
Select Column Auditing/Logging Jeremy Brown <jwbrown77@yahoo.com>
Re: Select Column Auditing/Logging Jeff Davis <pgsql@j-davis.com>
Re: Select Column Auditing/Logging Jeff Davis <pgsql@j-davis.com>
Re: Select Column Auditing/Logging Sam Mason <sam@samason.me.uk>
On Wed, 2009-07-22 at 14:41 -0700, Jeff Davis wrote: > On Wed, 2009-07-22 at 12:04 -0700, Jeremy Brown wrote: > > It seems that PostgreSQL can audit INSERT, UPDATE, DELETE, and > > TRUNCATE through the use of triggers. But SELECT triggers are > > unsupported (it does suggest perhaps using RULES). > > One thing you can do is use a set-returning function that, as a side > effect, records what happened. I should warn you not to record it in a transactional way: it must go out to an external service, or go back to postgresql using something like dblink. Otherwise, someone could do: BEGIN; SELECT ...; ROLLBACK; and whatever you logged would be gone. Regards, Jeff Davis
В списке pgsql-general по дате отправления
От: Knut P. Lehre
Дата: