From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: standalone backend PANICs during recovery |
Date: | 2016-08-30 06:47:25 |
Message-ID: | CAB7nPqTWSW83pDu1VOgzG4ikM+_Da9AwFCgEWHWmgv87tp2FoA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 24, 2016 at 5:07 PM, Bernd Helmle <mailings(at)oopsware(dot)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 | Content-Type | Size |
---|---|---|
standalone-no-recovery.patch | application/x-patch | 747 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-08-30 06:54:47 | Re: multivariate statistics (v19) |
Previous Message | Heikki Linnakangas | 2016-08-30 06:42:39 | Re: OpenSSL 1.1 breaks configure and more |