Postgres Pro
Downloads
Home   >   mailing lists

RE: Using per-transaction memory contexts for storing decoded tuples - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Using per-transaction memory contexts for storing decoded tuples
Date
Msg-id TYAPR01MB56925DAC31D4356EE32CDD9EF5612@TYAPR01MB5692.jpnprd01.prod.outlook.com
Whole thread Raw
Responses Re: Using per-transaction memory contexts for storing decoded tuples
List pgsql-hackers
Tree view 
Hi,

> We have several reports that logical decoding uses memory much more
> than logical_decoding_work_mem[1][2][3]. For instance in one of the
> reports[1], even though users set logical_decoding_work_mem to
> '256MB', a walsender process was killed by OOM because of using more
> than 4GB memory.

I appreciate your work on logical replication and am interested in the thread.
I've heard this issue from others, and this has been the barrier to using logical
replication. Please let me know if I can help with benchmarking, other
measurements, etc.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Regression tests fail with tzdata 2024b
Next
From: Alexander Lakhin
Date:
Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed