Re: Logical Replication of sequences
От | Amit Kapila |
---|---|
Тема | Re: Logical Replication of sequences |
Дата | |
Msg-id | CAA4eK1Ktxk_jXfen+py5n1Trj5anorPu_TsjQGv8z5h3G4VP6A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logical Replication of sequences (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Logical Replication of sequences
|
Список | pgsql-hackers |
On Wed, Jun 5, 2024 at 9:13 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Tue, Jun 4, 2024 at 8:56 PM Yogesh Sharma > <yogesh.sharma@catprosystems.com> wrote: > > > > On 6/4/24 06:57, Amit Kapila wrote: > > > > > 2. Provide a command say Alter Subscription ... Replicate Sequences > > > (or something like that) which users can perform before shutdown of > > > the publisher node during upgrade. This will allow copying all the > > > sequences from the publisher node to the subscriber node directly. > > > Similar to previous approach, this could also be inconvenient for > > > users. > > > > This is similar to option 1 except that it is a SQL command now. > > > > Right, but I would still prefer a command as it provides clear steps > for the upgrade. Users need to perform (a) Replicate Sequences for a > particular subscription (b) Disable that subscription (c) Perform (a) > and (b) for all the subscriptions corresponding to the publisher we > want to shut down for upgrade. > Another advantage of this approach over just a plain tool to copy all sequences before upgrade is that here we can have the facility to copy just the required sequences. I mean the set sequences that the user has specified as part of the publication. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: