From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |
Date: | 2025-04-16 18:43:59 |
Message-ID: | CANzqJaAm_HSUxRVM7DvMDOVPY4Up3yKTcMa0pQ6SAJ7BFk2qGQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You'll have to bring that up with the PgAudit maintainer. Note, though,
that the purpose of PgAudit is not "recreate the database from audit logs";
it's "what Auditors care about". In my experience, auditors do not care
about COMMIT and ROLLBACK statements.
On Wed, Apr 16, 2025 at 1:35 PM Achilleas Mantzios <
a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:
> On 16/4/25 15:36, Ron Johnson wrote:
>
>
> pgaudit is statement-level, not transaction-level; that's its nature.
> This is the same as log_statement.
>
> ok, but log_statement prints ROLLBACKs/COMMITs, but pgaudit not.
>
>
> On Wed, Apr 16, 2025 at 5:10 AM Achilleas Mantzios - cloud <
> a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:
>
>> On 4/15/25 12:14, KENAN ÇİFTÇİ wrote:
>>
>> Hi,
>>
>> You can use pgaudit and pgauditlogtofile extension (
>> https://github.com/fmbiete/pgauditlogtofile) together to write audit
>> logs in a separate file.
>>
>> One issue we have with pgaudit is that it prints AUDIT records even if
>> the xaction gets rollbacked, how do you alleviate that ?
>>
>>
>> yours,
>>
>> Kenan Çiftçi
>>
>> On Tue, Apr 15, 2025 at 1:44 PM vijay patil <vijay(dot)postgres(at)gmail(dot)com>
>> wrote:
>>
>>> Hi All,
>>>
>>> We are exploring auditing solutions for our PostgreSQL database and are
>>> considering using pgaudit for this purpose. However, we have a few
>>> questions:
>>>
>>> 1.
>>>
>>> *What is the best tool for auditing PostgreSQL databases?*
>>> -
>>>
>>> We are specifically looking for a solution that offers detailed
>>> auditing capabilities and is compatible with our setup.
>>> 2.
>>>
>>> *Can we store the audit information separately from PostgreSQL logs
>>> if we decide to use pgaudit?*
>>> -
>>>
>>> We would prefer to keep the audit logs in a separate file or
>>> location for easier management and analysis.
>>>
>>>
>>> We appreciate any help or suggestions!
>>>
>>>
>>> Thanks
>>>
>>> Vijay
>>>
>>
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>
>
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2025-04-16 18:57:17 | Re: Help with PhD Dissertation |
Previous Message | Adrian Klaver | 2025-04-16 18:07:37 | Re: Cannot turn track_counts on |