public inbox for [email protected]
help / color / mirror / Atom feedRe: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
3+ messages / 3 participants
[nested] [flat]
* Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
@ 2025-04-16 09:10 Achilleas Mantzios - cloud <[email protected]>
2025-04-16 12:36 ` Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately Ron Johnson <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Achilleas Mantzios - cloud @ 2025-04-16 09:10 UTC (permalink / raw)
To: [email protected]
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 <[email protected]>
> 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
>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
2025-04-16 09:10 Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately Achilleas Mantzios - cloud <[email protected]>
@ 2025-04-16 12:36 ` Ron Johnson <[email protected]>
2025-04-16 17:35 ` Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately Achilleas Mantzios <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Ron Johnson @ 2025-04-16 12:36 UTC (permalink / raw)
To: pgsql-generallists.postgresql.org <[email protected]>
pgaudit is statement-level, not transaction-level; that's its nature. This
is the same as log_statement.
On Wed, Apr 16, 2025 at 5:10 AM Achilleas Mantzios - cloud <
[email protected]> 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 <[email protected]>
> 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!
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
2025-04-16 09:10 Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately Achilleas Mantzios - cloud <[email protected]>
2025-04-16 12:36 ` Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately Ron Johnson <[email protected]>
@ 2025-04-16 17:35 ` Achilleas Mantzios <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Achilleas Mantzios @ 2025-04-16 17:35 UTC (permalink / raw)
To: [email protected]
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
> <[email protected]> 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
>> <[email protected]> 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!
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-04-16 17:35 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-04-16 09:10 Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately Achilleas Mantzios - cloud <[email protected]>
2025-04-16 12:36 ` Ron Johnson <[email protected]>
2025-04-16 17:35 ` Achilleas Mantzios <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox