Re: BUG #15989: Cluster unable to open as hot standby after SIGKILLduring exclusive backup

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: BUG #15989: Cluster unable to open as hot standby after SIGKILLduring exclusive backup
Дата
Msg-id 20190903163043.GO16436@tamriel.snowman.net
обсуждение исходный текст
Ответ на BUG #15989: Cluster unable to open as hot standby after SIGKILL during exclusive backup  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Greetings,

* PG Bug reporting form (noreply@postgresql.org) wrote:
> * Enable exclusive backup
> psql -c "select pg_start_backup('')"
>
> * Find pid of main postgres process
> ps -ef | grep 'postgres -D'
>
> * Send SIGKILL to found pid
> kill -s KILL <pid>

Don't kill the postmaster and don't use exclusive backup (which has been
deprecated, due specifically in part to the issue that it causes
problems on a crash).

> This is particularly a problem when running postgres in Docker, as Docker
> will send SIGKILL if database shutdown takes more than a few seconds.

You'll want to fix that then.

Thanks,

Stephen

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Memory leak in formatting.c
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries