From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
---|---|
To: | "wangw(dot)fnst(at)fujitsu(dot)com" <wangw(dot)fnst(at)fujitsu(dot)com> |
Cc: | Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
Subject: | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |
Date: | 2023-01-31 11:00:48 |
Message-ID: | CAJpy0uBkrY0QYjpCdTTQi3d3QYUSgS-Asju8fjADpnrap+euyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 31, 2023 at 3:57 PM wangw(dot)fnst(at)fujitsu(dot)com
<wangw(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Mon, Jan 23, 2023 21:00 PM Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com> wrote:
> > Hi,
> >
> > Thanks for your review.
> > Attached updated versions of the patches.
>
> Thanks for updating the patch set.
>
> > > 5. New member "created_slot" in structure LogicalRepWorker
> > > + /*
> > > + * Indicates if the sync worker created a replication slot or it reuses an
> > > + * existing one created by another worker.
> > > + */
> > > + bool created_slot;
> > >
> Yes, I think it makes sense. Thanks for the detailed explanation.
> I think I misunderstood the second half of the comment. I previously thought it
> meant that it was also true when reusing an existing slot.
>
I agree with Wang-san that the comment is confusing, I too
misunderstood it initially during my first run of the code. Maybe it
can be improved.
'Indicates if the sync worker created a replication slot for itself;
set to false if sync worker reuses an existing one created by another
worker'
thanks
Shveta
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2023-01-31 11:03:54 | Re: [PoC] Let libpq reject unexpected authentication requests |
Previous Message | David Rowley | 2023-01-31 10:46:05 | Re: heapgettup() with NoMovementScanDirection unused in core? |