logical replication out of memory

From: James Pang <jamespang886(at)gmail(dot)com>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: logical replication out of memory
Date: 2024-07-31 02:17:41
Message-ID: CAHgTRfd=5UrbADKFiShFeM517Y4+Q+xynDyRYBSmaHNr70R8rQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

2024-07-31 00:01:02.795
UTC:10.240.6.139(33068):repl13801(at)pgpodb:[3603770]:[10-1]:pgreps_13801ERROR:
out of memory
2024-07-31 00:01:02.795
UTC:10.240.6.139(33068):repl13801(at)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(at)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(at)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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message James Pang 2024-07-31 02:30:19 Re: logical replication out of memory
Previous Message Pavel Stehule 2024-07-30 20:56:19 Re: proposal: schema variables