From: | Daulat <daulat(dot)dba(at)gmail(dot)com> |
---|---|
To: | Holger Jakobs <holger(at)jakobs(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Separate log_destination, user specific |
Date: | 2022-01-25 11:26:04 |
Message-ID: | CALfOM6Ky=wdL_FKjyJX_5jxO=iqa1Wy_oyrubezz17ZFHyPaBA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks All !
I don't want to loss any messages. I just want to track the dba user ( some
users) actions and to generate a report.
On Tue, 25 Jan, 2022, 4:30 pm Holger Jakobs, <holger(at)jakobs(dot)com> wrote:
> Am 25.01.22 um 11:57 schrieb Paul Smith:
>
> On 25/01/2022 10:48, Daulat wrote:
>
> Is it possible to set a separate log_destination for some users in
> Postgres?
> As I know all actions are recorded under the directory specified
> by log_destination.
>
> But I want to create a separate log file for DBA users to log their
> actions.
> Is any third party or free ware tool available to accomplish this task ?
>
>
> Could you set PostgreSQL to log to Syslog, and then set up filters in
> rsyslog?
> (I've not done it, but it sounds like it may work)
>
> Using syslog is not advisable. Qutoe from
> https://www.postgresql.org/docs/current/runtime-config-logging.html
>
> The logging collector is designed to never lose messages. This means that
> in case of extremely high load, server processes could be blocked while
> trying to send additional log messages when the collector has fallen
> behind. In contrast, syslog prefers to drop messages if it cannot write
> them, which means it may fail to log some messages in such cases but it
> will not block the rest of the system.
>
> Do you really want to lose messages??
>
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Cawley | 2022-01-25 15:54:44 | Question about blocks. |
Previous Message | Holger Jakobs | 2022-01-25 11:00:44 | Re: Separate log_destination, user specific |