From: S Hoffman <hoffman7043@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Lucio Chiessi <lucio.chiessi@trustly.com>
Cc: PGSql Admin list <pgsql-admin@lists.postgresql.org>
Subject: Re: Another way to do audit in DML operations in PostgreSQL >= 14
Date: Fri, 23 Feb 2024 11:35:04 -0800
Message-ID: <17797068-0325-47A4-AF8E-8CA820CB84E4@gmail.com> (raw)
In-Reply-To: <ZdiryzCPve7wcZIC@momjian.us>
References: <ZdiryzCPve7wcZIC@momjian.us>
A remote syslog is a good option, too. The method depends on the specific needs, resources, and infrastructure. Remote Syslog can be easier to set up. External logging solutions scale better, offer more analytical features, and can allocate more resources to log management.
Try testing these approaches in a staging environment to assess their impact on performance and to ensure they meet compliance needs. That will be the best approach to determine the most beneficial solution.
Kind regards,
Sondra
Sent from my iPhone
> On Feb 23, 2024, at 6:29 AM, Bruce Momjian <bruce@momjian.us> wrote:
>
> On Thu, Feb 22, 2024 at 08:54:52PM -0800, S Hoffman wrote:
>> Hi Lucio Chiessi,
>>
>> Dealing with large volumes of data can be a challenging task. If you struggle
>> with this issue, one possible solution is to consider using external logging
>> services. Specifically, asynchronous logging services or external logging
>> services that are designed to handle streaming data may be effective options to
>> explore. Some popular external logging services in this regard include
>> Elasticsearch and Spunk, known for their ability to handle large volumes of
>> data. If you have any questions or want to explore other options, please let me
>> know.
>
> Would remote syslog be an option too?
>
> --
> Bruce Momjian <bruce@momjian.us> https://momjian.us
> EDB https://enterprisedb.com
>
> Only you can decide what is important to you.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: hoffman7043@gmail.com, bruce@momjian.us, lucio.chiessi@trustly.com, pgsql-admin@lists.postgresql.org
Subject: Re: Another way to do audit in DML operations in PostgreSQL >= 14
In-Reply-To: <17797068-0325-47A4-AF8E-8CA820CB84E4@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox