Re: PG Upgrade with hardlinks, when to start/stop master and replicas

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: PG Upgrade with hardlinks, when to start/stop master and replicas
Дата
Msg-id 20190219150538.GP6197@tamriel.snowman.net
обсуждение исходный текст
Ответ на Re: PG Upgrade with hardlinks, when to start/stop master and replicas  (Hellmuth Vargas <hivs77@gmail.com>)
Ответы Re: PG Upgrade with hardlinks, when to start/stop master and replicas  (Hellmuth Vargas <hivs77@gmail.com>)
Список pgsql-general
Greetings,

* Hellmuth Vargas (hivs77@gmail.com) wrote:
> But could you do the following procedure?:

> pg_upgrade of the master
> rysnc with a hot standby

The above should be alright provided both the primary and the standby
are down and the instructions in the pg_upgrade docs are followed.

> arracar master
> hot standby start

So, start both the primary and the replica?  That part should be fine by
itself.

> stop hot standby and rsync the other hot standby with the migrated hot
> standby?

At some later point, shut down the replica completely, then do an rsync
from that replica to the other replica and build its hard-link tree that
way, and update anything that's changed while the 'migrated' replica was
online?  I don't see any obvious issue with that as the result should
mean that the two replicas are identical from PG's perspective from that
point moving forward.

Ultimately, it really depends on your specific environment though, of
course.  It also might not be a bad idea to do a regular backup of the
upgraded primary and then restore that to the second replica, just to
make sure you have that whole process working and to test out your
restore process.

Thanks!

Stephen

Вложения

В списке pgsql-general по дате отправления:

Предыдущее
От: Hellmuth Vargas
Дата:
Сообщение: Re: PG Upgrade with hardlinks, when to start/stop master and replicas
Следующее
От: Hellmuth Vargas
Дата:
Сообщение: Re: PG Upgrade with hardlinks, when to start/stop master and replicas