From: Christoph Berg <myon@debian.org>
To: Yuriy Chernyshov <georgthegreat@gmail.com>
Cc: pgsql-pkg-debian@postgresql.org
Subject: Re: pg_upgradecluster fails if port is not specified in postgresql.conf
Date: Tue, 15 May 2018 10:29:11 +0200
Message-ID: <20180515082911.GA25563@msg.df7cb.de> (raw)
In-Reply-To: <CAPHLbgMZdoMkWe6wAMQn2By-9d95T6QKPDBGF5x6nTkAcK4ExA@mail.gmail.com>
References: <CAPHLbgMZdoMkWe6wAMQn2By-9d95T6QKPDBGF5x6nTkAcK4ExA@mail.gmail.com>
Re: Yuriy Chernyshov 2018-05-14 <CAPHLbgMZdoMkWe6wAMQn2By-9d95T6QKPDBGF5x6nTkAcK4ExA@mail.gmail.com>
> It looks like postgres falls back to default port (5432) if port is not
> specified in postgresql.conf.
> The probles is actual in postgresql-common=191.pgdg14.04+1
>
> Unfortunately, pg_upgradecluster does not handle this situation. It fails
> with "Error: could not get cluster locales" and such message hardly helps
> to debug the problem.
Hi,
where did you specify the port if not in postgresql.conf?
Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-pkg-debian@postgresql.org
Cc: myon@debian.org, georgthegreat@gmail.com
Subject: Re: pg_upgradecluster fails if port is not specified in postgresql.conf
In-Reply-To: <20180515082911.GA25563@msg.df7cb.de>
References: <CAPHLbgMZdoMkWe6wAMQn2By-9d95T6QKPDBGF5x6nTkAcK4ExA@mail.gmail.com> <20180515082911.GA25563@msg.df7cb.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox