Re: Synchronizing slots from primary to standby
| От | Drouvot, Bertrand |
|---|---|
| Тема | Re: Synchronizing slots from primary to standby |
| Дата | |
| Msg-id | 8e7ef746-2b94-4cc0-a4c0-43387ee6bc4e@gmail.com обсуждение исходный текст |
| Ответ на | Re: Synchronizing slots from primary to standby (shveta malik <shveta.malik@gmail.com>) |
| Ответы |
Re: Synchronizing slots from primary to standby
|
| Список | pgsql-hackers |
Hi, On 11/21/23 10:32 AM, shveta malik wrote: > On Tue, Nov 21, 2023 at 2:02 PM shveta malik <shveta.malik@gmail.com> wrote: >> > v37 fails to apply to HEAD due to a recent commit e83aa9f92fdd, > rebased the patches. PFA v37_2 patches. Thanks! Regarding the promotion flow: If the primary is available and reachable I don't think we currently try to ensure that slots are in sync. I think we'd miss the activity since the last sync and the promotion request or am I missing something? If the primary is available and reachable shouldn't we launch a last round of synchronization (skipping all the slots that are not in 'r' state)? Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: