From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Petr Jelinek <petr(dot)jelinek(at)enterprisedb(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com> |
Subject: | Re: Single transaction in the tablesync worker? |
Date: | 2021-01-07 08:11:45 |
Message-ID: | CAHut+PvdR0PjCyY7ieqRySF5yjUaQx2bU+wNum2uSiseyrd61Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2021 at 2:07 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> Okay, if we want to go that way then we should add some documentation
> about it. Currently, the slot name used by apply worker is known to
> the user because either it is specified by the user or the default is
> subscription name, so the user can manually remove that slot later but
> that is not true for tablesync slots. I think we need to update both
> the Drop Subscription page [1] and logical-replication-subscription
> page [2] where we have mentioned temporary slots and in the end "Here
> are some scenarios: .." to mention about these slots and probably how
> their names are generated so that in such special situations users can
> drop them manually.
>
> [1] - https://www.postgresql.org/docs/devel/sql-dropsubscription.html
> [2] - https://www.postgresql.org/docs/devel/logical-replication-subscription.html
>
PG docs updated in latest patch [v12]
Kind Regards,
Peter Smith.
Fujitsu Australia
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2021-01-07 08:16:32 | Re: [HACKERS] [PATCH] Generic type subscripting |
Previous Message | Peter Smith | 2021-01-07 08:08:21 | Re: Single transaction in the tablesync worker? |