Re: logical replication out of memory - Mailing list pgsql-performance

From James Pang
Subject Re: logical replication out of memory
Date
Msg-id CAHgTRffDMmpZfpGNQ_WSRe1juK2M8wC5CkWJBW+g7dtZbQ27EQ@mail.gmail.com
Whole thread Raw
In response to logical replication out of memory  (James Pang <jamespang886@gmail.com>)
List pgsql-performance

    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" ?   or we have drop replication slots or make it start from a new pglsn position ? 


2024-07-31 00:01:02.795 UTC:xxx.xxxx.xxx.xxx(33068):repl13801@pgpodb:[3603770]:[10-1]:pgreps_13801ERROR:  out of memory

2024-07-31 00:01:02.795 UTC:xxx.xxxx.xxx.xxx(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:xxx.xxxx.xxx.xxx(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:xxx.xxxx.xxx.xxx(33068):repl13801@pgpodb:[3603770]:[13-1]:pgreps_13801STATEMENT:  START_REPLICATION SLOT "pgreps_13801" LOGICAL 3C/F24C74D0 (proto_version '1', publication_names 'pgreps_13801')



James Pang (chaolpan) <chaolpan@cisco.com> 於 2024年7月31日週三 上午10:28寫道:

 

 

From: James Pang <jamespang886@gmail.com>
Sent: Wednesday, July 31, 2024 10:18 AM
To: pgsql-performance@lists.postgresql.org
Subject: logical replication out of memory

 

 

 

2024-07-31 00:01:02.795 UTC:xxx.xxxx.xxx.xxx(33068):repl13801@pgpodb:[3603770]:[10-1]:pgreps_13801ERROR:  out of memory

2024-07-31 00:01:02.795 UTC:xxx.xxxx.xxx.xxx(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:xxx.xxxx.xxx.xxx(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:xxx.xxxx.xxx.xxx(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" ?

pgsql-performance by date:

Previous
From: James Pang
Date:
Subject: logical replication out of memory
Next
From: khan Affan
Date:
Subject: Re: logical replication out of memory