Re: auditing in rds or triggers that write to pg_log

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 18:16:44
Message-ID: CAEfeRhXNjfXYhh+kNONoqipr2pAEP58wG_4mvOb4ferYWRdDOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Mike:
You would also want to check the documentation on Error Reporting and
Logging
https://www.postgresql.org/docs/current/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHEN
Take a look on client_min_messages that can be set on a per session basis.

Regards,
Walter

On Thu, Mar 9, 2017 at 2:51 PM, Mike Broers <mbroers(at)gmail(dot)com> wrote:

> 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
>>>
>>>
>>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Stéphane KANSCHINE 2017-03-10 04:36:04 Re: cfg pg_stat_statements in PG 9.5 error
Previous Message ghiureai 2017-03-09 18:12:40 Re: cfg pg_stat_statements in PG 9.5 error