Re: pg_upgradecluster fails if port is not specified in postgresql.conf

From: Yuriy Chernyshov <georgthegreat(at)gmail(dot)com>
To: myon(at)debian(dot)org, pgsql-pkg-debian(at)postgresql(dot)org
Subject: Re: pg_upgradecluster fails if port is not specified in postgresql.conf
Date: 2018-05-15 08:36:27
Message-ID: CAPHLbgP9QZT45Ka0SfBO=KmaMYAXPEg+edjT9LASiPcpp+ZvGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-debian

Hi,

it looks like postgres defaults to port 5432 if nothing is specified in
config.
This was my configuration.

postgresql also supports conf.d folder which can contain additional
setting. It looks like pg_upgradecluster does not support this folder
either (yet it was not my case).

On Tue, 15 May 2018 at 11:29, Christoph Berg <myon(at)debian(dot)org> wrote:

> Re: Yuriy Chernyshov 2018-05-14 <
> CAPHLbgMZdoMkWe6wAMQn2By-9d95T6QKPDBGF5x6nTkAcK4ExA(at)mail(dot)gmail(dot)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
>

In response to

Browse pgsql-pkg-debian by date

  From Date Subject
Next Message apt.postgresql.org repository 2018-05-15 10:03:21 pgmodeler updated to version 0.9.1-1.pgdg+1
Previous Message Christoph Berg 2018-05-15 08:29:11 Re: pg_upgradecluster fails if port is not specified in postgresql.conf