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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: jlucasdba(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15989: Cluster unable to open as hot standby after SIGKILL during exclusive backup
Date: 2019-09-03 16:30:43
Message-ID: 20190903163043.GO16436@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greetings,

* PG Bug reporting form (noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2019-09-04 07:53:05 Re: BUG #15977: Inconsistent behavior in chained transactions
Previous Message fn ln 2019-09-03 13:27:49 Re: BUG #15977: Inconsistent behavior in chained transactions