logical replication out of memory - Mailing list pgsql-performance

From James Pang
Subject logical replication out of memory
Date
Msg-id CAHgTRfd=5UrbADKFiShFeM517Y4+Q+xynDyRYBSmaHNr70R8rQ@mail.gmail.com
Whole thread Raw
Responses Re: logical replication out of memory
List pgsql-performance
2024-07-31 00:01:02.795 UTC:10.240.6.139(33068):repl13801@pgpodb:[3603770]:[10-1]:pgreps_13801ERROR:  out of memory
2024-07-31 00:01:02.795 UTC:10.240.6.139(33068):repl13801@pgpodb:[3603770]:[11-1]:pgreps_13801DETAIL:  Cannot enlarge string buffer containing 378355896 bytes by 756711422 more bytes.
2024-07-31 00:01:02.795 UTC:10.240.6.139(33068):repl13801@pgpodb:[3603770]:[12-1]:pgreps_13801CONTEXT:  slot "pgreps_13801", output plugin "pgoutput", in the change callback, associated LSN 3D/318438E0
2024-07-31 00:01:02.795 UTC:10.240.6.139(33068):repl13801@pgpodb:[3603770]:[13-1]:pgreps_13801STATEMENT:  START_REPLICATION SLOT "pgreps_13801" LOGICAL 3C/F24C74D0 (proto_version '1', publication_names 'pgreps_13801')

We use built-in pgoutput and a client application did an HOT update to a column , that data type is "text" and real length is 756711422.  But this table is NOT on publication list, possible to make logical decoding ignore "WAL records belong to tables that's not in publication list" ? 

Thanks,

James 

pgsql-performance by date:

Previous
From: Jon Zeppieri
Date:
Subject: Re: Help with row estimate problem
Next
From: James Pang
Date:
Subject: Re: logical replication out of memory