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_
chaolpan) 於 2024年7月31日週三 上午10:28寫道：
>
>
>
>
> *From:* James Pang
> *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
>
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.
