o
> "NOT in replication list" tables ? that can help reduce this kind of
> error.
>
> Thanks,
>
> James
>
>
>>
>>
>>
>> *From:* khan Affan
>> *Sent:* Wednesday, July 31, 2024 1:42 PM
>> *To:* James Pang
>> *Cc:* pgsql-
From:* khan Affan
> *Sent:* Wednesday, July 31, 2024 1:42 PM
> *To:* James Pang
> *Cc:* pgsql-performance@lists.postgresql.org
> *Subject:* Re: logical replication out of memory
>
>
>
> Hi Pang
>
> The text column is exceptionally large, Your server must be out of memory,
Hi Pang
The text column is exceptionally large, Your server must be out of memory,
Such a process ran out of memory while handling a large text column update.
I suggest using an S3 bucket for such files, Consider increasing the
memory-related configuration parameters, like work_mem, maintenance_
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
h
