| From: | Cachique <cachique(at)gmail(dot)com> |
|---|---|
| To: | Mike Broers <mbroers(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: auditing in rds or triggers that write to pg_log |
| Date: | 2017-03-09 17:49:59 |
| Message-ID: | CAEfeRhX25DY58TKA_3PrsEGsdJRoUscUtaNtBQgHez=Hkar8JQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Mike.
In any of your plpgsql function you can use RAISE LOG 'Blah, Blah...' the
same way you use RAISE NOTICE.
All this text go directly to your standard postgresql log file.
Regards,
Walter
On Thu, Mar 9, 2017 at 2:37 PM, Mike Broers <mbroers(at)gmail(dot)com> wrote:
> I'm investigating ways to track all interactions with certain tables in
> postgres. pgaudit seems like a great solution but it doesnt look like its
> a supported extension in rds yet.
>
> I've considered creating triggers that record interactions into the
> standard postgresql log file but I cant find examples of this approach,
> only examples that write to tables. Is it possible to do this?
>
> Thanks
> Mike
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Broers | 2017-03-09 17:51:53 | Re: auditing in rds or triggers that write to pg_log |
| Previous Message | ghiureai | 2017-03-09 17:49:04 | Re: cfg pg_stat_statements in PG 9.5 error |