| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mai Peng <maily(dot)peng(at)webedia-group(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Cc: | Dorian Yahouedeou <dorian(dot)yahouedeou(at)ext(dot)webedia-group(dot)com> |
| Subject: | Re: Transaction size and Wal2Json |
| Date: | 2019-02-07 10:45:58 |
| Message-ID: | 7b3ad474-bdf2-11fb-c53d-add6882333ed@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mariel Cherkassky | 2019-02-07 11:55:34 | Re: autovacuum big table taking hours and sometimes seconds |
| Previous Message | Mai Peng | 2019-02-07 10:38:01 | Transaction size and Wal2Json |