pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedTransaction size and Wal2Json
2+ messages / 2 participants
[nested] [flat]
* Transaction size and Wal2Json
@ 2019-02-07 10:38 Mai Peng <maily.peng@webedia-group.com>
2019-02-07 10:45 ` Re: Transaction size and Wal2Json Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 2+ messages in thread
From: Mai Peng @ 2019-02-07 10:38 UTC (permalink / raw)
To: pgsql-performance; +Cc: Dorian Yahouedeou <dorian.yahouedeou@ext.webedia-group.com>
Hello,
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 ?
Thank you
Mai
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Transaction size and Wal2Json
2019-02-07 10:38 Transaction size and Wal2Json Mai Peng <maily.peng@webedia-group.com>
@ 2019-02-07 10:45 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 2+ messages in thread
From: Peter Eisentraut @ 2019-02-07 10:45 UTC (permalink / raw)
To: Mai Peng <maily.peng@webedia-group.com>; pgsql-performance; +Cc: Dorian Yahouedeou <dorian.yahouedeou@ext.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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2019-02-07 10:45 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-02-07 10:38 Transaction size and Wal2Json Mai Peng <maily.peng@webedia-group.com>
2019-02-07 10:45 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
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