From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Mai Peng <maily.peng@webedia-group.com>
To: pgsql-performance@postgresql.org
Cc: Dorian Yahouedeou <dorian.yahouedeou@ext.webedia-group.com>
Subject: Re: Transaction size and Wal2Json
Date: Thu, 7 Feb 2019 11:45:58 +0100
Message-ID: <7b3ad474-bdf2-11fb-c53d-add6882333ed@2ndquadrant.com> (raw)
In-Reply-To: <E4B1FAE2-6E72-495C-A470-4224CE063C4D@webedia-group.com>
References: <E4B1FAE2-6E72-495C-A470-4224CE063C4D@webedia-group.com>
On 07/02/2019 11:38, Mai Peng wrote:
> We use the plugin Wal2Json in order to catch every modification on database. We’ve got an issue : WAL were growing very fast, the state of pg_stat_replication still on ‘catchup’ , an error:pg_recvlogical: unexpected termination of replication stream: ERROR: out of memory DETAIL: Cannot enlarge string buffer. It seems Wal2Json can not handle very big transactions ( more than 1 Gb).
> How could we measure the size of a transaction ?
> Could we increase this limitation ?
You should send a bug report to wal2json.
It's plausible that some naive coding would run into the limitation that
you describe, but a bit of effort can probably solve it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-performance@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, maily.peng@webedia-group.com, dorian.yahouedeou@ext.webedia-group.com
Subject: Re: Transaction size and Wal2Json
In-Reply-To: <7b3ad474-bdf2-11fb-c53d-add6882333ed@2ndquadrant.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