On Fri, May 21, 2021 at 6:47 PM Guillaume Lelarge
wrote:
>
> Le ven. 21 mai 2021 à 05:43, Amit Kapila a écrit :
>>
>> On Fri, May 21, 2021 at 1:30 AM Guillaume Lelarge
>> wrote:
>> >
>> >
>> >> If so, the
>> >> problem might be that copying the data of the first table creates a
>> >> transaction
Le ven. 21 mai 2021 à 05:43, Amit Kapila a écrit :
> On Fri, May 21, 2021 at 1:30 AM Guillaume Lelarge
> wrote:
> >
> >
> >> If so, the
> >> problem might be that copying the data of the first table creates a
> >> transaction which blocks creation of the slot for second table copy.
> >
> >
> > I
On Fri, May 21, 2021 at 1:30 AM Guillaume Lelarge
wrote:
>
>
>> If so, the
>> problem might be that copying the data of the first table creates a
>> transaction which blocks creation of the slot for second table copy.
>
>
> I don't understand how a transaction could block the creation of a slot.
Hi,
Le jeu. 20 mai 2021 à 12:09, Amit Kapila a écrit :
> On Wed, Apr 28, 2021 at 2:43 PM Guillaume Lelarge
> wrote:
> >
> > And it logs the "still waiting" message as long as the first table is
> being synchronized. Once this is done, it releases the lock, and the
> synchronization of the secon
On Wed, Apr 28, 2021 at 2:43 PM Guillaume Lelarge
wrote:
>
> And it logs the "still waiting" message as long as the first table is being
> synchronized. Once this is done, it releases the lock, and the
> synchronization of the second table starts.
>
> Is there something I didn't understand on th
Le mer. 28 avr. 2021 à 11:37, Guillaume Lelarge a
écrit :
> Le mer. 28 avr. 2021 à 11:12, Guillaume Lelarge
> a écrit :
>
>> Hi,
>>
>> One of my customers has an issue with logical replication. As $SUBJECT
>> says, multiple table synchronization happens serially. To be honest, it
>> doesn't do t
Le mer. 28 avr. 2021 à 11:12, Guillaume Lelarge a
écrit :
> Hi,
>
> One of my customers has an issue with logical replication. As $SUBJECT
> says, multiple table synchronization happens serially. To be honest, it
> doesn't do this every time. It happens when the tables are big enough.
>
> This is