Date: Fri, 23 Feb 2024 09:29:31 -0500
From: Bruce Momjian <bruce@momjian.us>
To: S Hoffman <hoffman7043@gmail.com>
Cc: Lucio Chiessi <lucio.chiessi@trustly.com>,
	PGSql Admin list <pgsql-admin@lists.postgresql.org>
Subject: Re: Another way to do audit in DML operations in PostgreSQL >= 14
Message-ID: <ZdiryzCPve7wcZIC@momjian.us>
References: 
 <CADoTbHWMXZfuDDHQU__UhLLa51GSyNhNj0prNQ+BD2j83hFgkA@mail.gmail.com>
 <B0D1A942-4EAA-4DAC-9ADC-78D1F0FB9BB5@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B0D1A942-4EAA-4DAC-9ADC-78D1F0FB9BB5@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZdiryzCPve7wcZIC%40momjian.us>
Precedence: bulk

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.