Re: Synchronizing slots from primary to standby
| От | Dilip Kumar |
|---|---|
| Тема | Re: Synchronizing slots from primary to standby |
| Дата | |
| Msg-id | CAFiTN-skn=ffyC8PMzg7gfpyNLfx7v9roae-+W8HYbpzoO0mkg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Synchronizing slots from primary to standby (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
RE: Synchronizing slots from primary to standby
|
| Список | pgsql-hackers |
On Fri, Jan 5, 2024 at 5:45 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Fri, Jan 5, 2024 at 4:25 PM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > > > On Fri, Jan 5, 2024 at 8:59 AM shveta malik <shveta.malik@gmail.com> wrote: > > > > > I was going the the patch set again, I have a question. The below > > comments say that we keep the failover option as PENDING until we have > > done the initial table sync which seems fine. But what happens if we > > add a new table to the publication and refresh the subscription? In > > such a case does this go back to the PENDING state or something else? > > > > At this stage, such an operation is prohibited. Users need to disable > the failover option first, then perform the above operation, and after > that failover option can be re-enabled. Okay, that makes sense to me. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: