Re: standalone backend PANICs during recovery - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: standalone backend PANICs during recovery
Date
Msg-id CAB7nPqTWSW83pDu1VOgzG4ikM+_Da9AwFCgEWHWmgv87tp2FoA@mail.gmail.com
Whole thread Raw
In response to Re: standalone backend PANICs during recovery  (Bernd Helmle <mailings@oopsware.de>)
Responses Re: standalone backend PANICs during recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Aug 24, 2016 at 5:07 PM, Bernd Helmle <mailings@oopsware.de> wrote:
> That said, i'm okay if --single is not intended to bring up a hot standby.
> There are many other ways to debug such problems.

This patch is still on the CF app:
https://commitfest.postgresql.org/10/610/
Even after thinking about it, my opinion is still the same. Let's
prevent a standalone backend to start if it sees recovery.conf.
Attached is a patch and the CF entry is switched as ready for
committer to move on.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: OpenSSL 1.1 breaks configure and more
Next
From: Michael Paquier
Date:
Subject: Re: multivariate statistics (v19)