Re: pg_rewind vs superuser

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: pg_rewind vs superuser
Дата
Msg-id 20190408061725.GF2712@paquier.xyz
обсуждение исходный текст
Ответ на Re: pg_rewind vs superuser  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: pg_rewind vs superuser  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Re: pg_rewind vs superuser  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
On Sun, Apr 07, 2019 at 03:06:56PM +0200, Magnus Hagander wrote:
> So can we *detect* that this is the case? Because if so, we could perhaps
> just wait for it to be done? Because there will always be one?

Yes, this one is technically possible.  We could add a timeout option
which checks each N seconds the control file of the online source and
sees if its timeline differs or not with the target, waiting for the
change to happen.  If we do that, we may want to revisit the behavior
of not issuing an error if the source and the target are detected as
being on the same timeline, and consider it as a failure.

> The main point is -- we know from experience that it's pretty fragile to
> assume the user read the documentation :) So if we can find *any* way to
> handle this in code rather than docs, that'd be great. We would still
> absolutely want the docs change for back branches of course.

Any veeeeery recent experience on the matter perhaps? :)
--
Michael

Вложения

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

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: lazy_scan_heap() forgets to mark buffer dirty when setting all frozen?
Следующее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: Strange coding in _mdfd_openseg()