Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Thadeus Anand <thadeus(at)rmkv(dot)com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
Date: 2025-08-25 11:13:28
Message-ID: CAA4eK1JEOyMDKOgwU=ce0EMBvAC9j5zq1QR_BLcu8XmQENbCFw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Aug 25, 2025 at 3:34 PM Thadeus Anand <thadeus(at)rmkv(dot)com> wrote:
>
> The logical_decoding_work_mem at the publisher is currently set at 1 GB.
>
> I remember setting this a while ago as part of my struggle to get rid of the memory allocation issue.
>

Hmm, this means that your transaction size has a large number of
changes which leads to spilling of changes. This makes another
question of Kuroda-San more important, which is to show the size and
contents of pg_replslot. I have tried to check the fixes done in 17.5
and 17.6 but I don't see any obvious change which could lead to such a
problem. I could be missing something which we can try to find with
more information and probably if you can share a test.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thadeus Anand 2025-08-25 11:35:30 Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
Previous Message Thadeus Anand 2025-08-25 10:30:21 Re: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine