| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Đỗ Ngọc Trí Cường <seminoob(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Help with tracking! |
| Date: | 2010-04-19 05:52:44 |
| Message-ID: | 4BCBEFAC.3050502@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Đỗ Ngọc Trí Cường wrote:
> Dear all,
>
> I've a problem but I search all the help file and can't find the solution.
>
> I want to track all action of a specify role on all or one schema in
> database.
>
> Can you help me?
You can use statement-level logging, though there are no facilities in
statement-level logging to restrict what is logged to only one role's
activity.
You can use the usual audit triggers on database tables, which is what I
would recommend. Audit triggers in PostgreSQL cannot track reads
(SELECTs), only INSERT/UPDATE/DELETE and in 8.4 also TRUNCATE. They
cannot track ALTER/RENAME/DROP table, changes to sequences, etc. It is
trivial to write an audit trigger that only records anything when a user
is a member of a particular role.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | cojack | 2010-04-19 07:23:09 | Ltree - how to sort nodes on parent node |
| Previous Message | Đỗ Ngọc Trí Cường | 2010-04-19 02:26:53 | Help with tracking! |