From: | Mike Broers <mbroers(at)gmail(dot)com> |
---|---|
To: | Cachique <cachique(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:51:53 |
Message-ID: | CAB9893h3hAf7DUi=mTMXXqHZLjbe35DKcveZAVSMv19UKjFW=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I think this is exactly what i was looking for, thanks!!
On Thu, Mar 9, 2017 at 11:49 AM, Cachique <cachique(at)gmail(dot)com> wrote:
> 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 | Tom Lane | 2017-03-09 18:08:41 | Re: cfg pg_stat_statements in PG 9.5 error |
Previous Message | Cachique | 2017-03-09 17:49:59 | Re: auditing in rds or triggers that write to pg_log |