From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | thomas(at)thurman(dot)org(dot)uk, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15916: Confusing upgrade message |
Date: | 2019-07-28 00:47:44 |
Message-ID: | 20190728004744.diqvnlsr63iquq5b@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Jul 18, 2019 at 08:32:04AM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15916
> Logged by: Marnanel Thurman
> Email address: thomas(at)thurman(dot)org(dot)uk
> PostgreSQL version: 11.4
> Operating system: Debian
> Description:
>
> This happens with version 11.4-1.pgdg90+1 in
> http://apt.postgresql.org/pub/repos/apt/ .
>
> The upgrade process prints this message:
>
> Success. You can now start the database server using:
>
> pg_ctlcluster 11 main start
>
> But the server is restarted automatically, immediately afterwards. So the
> message is confusing, and should be suppressed.
Uh, my guess is that initdb is being run as pg_ctlcluster, but that
there is some wrapper around that that is starting the database after
the initdb. I think you need to report this as a bug to the people who
packaged this since pg_ctlcluster is Debian-specific. Was there any
output after this to indicate the server had been started?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-28 10:45:55 | Re: BUG #15883: Event Trigger Firing Matrix Table is incomplete |
Previous Message | Bruce Momjian | 2019-07-27 21:41:30 | Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented |