> On May 7, 2024, at 05:02, Amit Kapila wrote:
>
>
> In PG-14, we have added a feature in logical replication to stream
> long in-progress transactions which should reduce spilling to a good
> extent. You might want to try that.
That's been my principal recommendation (since that would also
On Tue, May 7, 2024 at 9:51 AM Ashutosh Bapat
wrote:
>
> On Tue, May 7, 2024 at 12:00 AM Christophe Pettus wrote:
>>
>> Thank you for the reply!
>>
>> > On May 1, 2024, at 02:18, Ashutosh Bapat
>> > wrote:
>> > Is there a large transaction which is failing to be replicated repeatedly
>> > -
On Tue, Apr 30, 2024 at 11:28 PM Christophe Pettus wrote:
>
> I wanted to check my understanding of how control flows in a walsender doing
> logical replication. My understanding is that the (single) thread in each
> walsender process, in the simplest case, loops on:
>
> 1. Pull a record out
On Tue, May 7, 2024 at 12:00 AM Christophe Pettus wrote:
> Thank you for the reply!
>
> > On May 1, 2024, at 02:18, Ashutosh Bapat
> wrote:
> > Is there a large transaction which is failing to be replicated
> repeatedly - timeouts, crashes on upstream or downstream?
>
> AFAIK, no, although I am
Thank you for the reply!
> On May 1, 2024, at 02:18, Ashutosh Bapat wrote:
> Is there a large transaction which is failing to be replicated repeatedly -
> timeouts, crashes on upstream or downstream?
AFAIK, no, although I am doing this somewhat by remote control (I don't have
direct access to
On Tue, Apr 30, 2024 at 11:28 PM Christophe Pettus wrote:
>
> Hi,
>
> I wanted to check my understanding of how control flows in a walsender
> doing logical replication. My understanding is that the (single) thread in
> each walsender process, in the simplest case, loops on:
>
> 1. Pull a
Hi,
I wanted to check my understanding of how control flows in a walsender doing
logical replication. My understanding is that the (single) thread in each
walsender process, in the simplest case, loops on:
1. Pull a record out of the WAL.
2. Pass it to the recorder buffer code, which,
3.
