VS: BUG #17218: Cluster recovery is not working properly.

Поиск
Список
Период
Сортировка
От Suhonen Reijo (Valtori)
Тема VS: BUG #17218: Cluster recovery is not working properly.
Дата
Msg-id cd85e0d6cdcc4b4a9457172652a17df0@valtori.fi
обсуждение исходный текст
Ответ на Re: BUG #17218: Cluster recovery is not working properly.  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-bugs
Дерево обсуждения

Hi,

 

Thanks for the information.

 

Regards,

 

Reijo Suhonen

 

 

Lähettäjä: Magnus Hagander <magnus@hagander.net>
Lähetetty: maanantai 11. lokakuuta 2021 13.12
Vastaanottaja: Suhonen Reijo (Valtori) <reijo.suhonen@valtori.fi>; PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Aihe: Re: BUG #17218: Cluster recovery is not working properly.

 

 

 

On Mon, Oct 11, 2021 at 12:09 PM PG Bug reporting form <noreply@postgresql.org> wrote:

The following bug has been logged on the website:

Bug reference:      17218
Logged by:          Reijo Suhonen
Email address:      reijo.suhonen@valtori.fi
PostgreSQL version: 14.0
Operating system:   Red Hat Enterprise Linux Server 7.9 (Maipo)
Description:       

Restoring a cluster to a specific point in time does not work. The restore
ends with the error message "FATAL, XX000," recovery ended before configured
recovery target was reached " and the cluster goes down.
The same test with version 12 works normally.

 

This doesn't look like a bug. You have specified a recovery target (09:28) that's beyond the end of what's in WAL (09:27:20). You shouldn't do that -- if you want to recover until the end of WAL, you shouldn't specify a target at all.

 

The behaviour of this case changed in PostgreSQL 13 which is probably why you didn't see it before. https://www.postgresql.org/docs/release/13.0/ has the entry "Generate an error if recovery does not reach the specified recovery target (Leif Gunnar Erlandsen, Peter Eisentraut) Previously, a standby would promote itself upon reaching the end of WAL, even if the target was not reached.".

 

--

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

Предыдущее
От: Zhihong Zhang
Дата:
Сообщение: Re: Epoch from age is incorrect
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #17223: Foreign key SET NULL depends on constraints order