[Pkg-postgresql-public] Bug#915965: Bug#915965: postgresql-11: postgresql listens on non-default port number 5433

[Ralf Jung]

Hi Christoph,

Thanks for the quick response!

> the port was not "changed". The old 10 cluster kept running on 5432,
> and the newly installed 11 cluster got 5433 assigned. At that point,
> you probably transferred the data from the 10 to the 11 cluster
> manually.

This is a development-only setup, so I think what happened is that I decided I
don't care about figuring out how migration works, I'll just uninstall the old
thing and that's fine.  There is no relevant data there anyway.  I did not,
however, expect the port to change (as an end-to-end effect of upgrading and
then uninstalling the old version).

The postgresql upgrade showed some message about migrations.  However, as
someone not very familiar with postgresql, that message was not useful to me: I
just did not understand what it tried to tell me.  It probably mentioned
"clusters" and my reaction was "I just have a single stand-alone server, not a
cluster, so probably this does not affect me -- and I don't care about the data
stored in there anyway, so whatever".  Maybe the wording of that message could
be improved.  Or maybe the process could be more automatic, like it is with
other databases?  (I've been running mysql servers across many upgrades and
never had to do anything manually on upgrades.)

> The proper "Debian" way to do that is via pg_upgradecluster, which
> will then also make sure that the upgraded cluster takes over the port
> of the original one.
> 
> This is documented in
> /usr/share/doc/postgresql-common/README.Debian.gz
I don't think you can expect people to read the README file of every package
they install (and postgresql alone consists of at least 3 packages).  I just
hope now that I will remember `pg_upgradecluster` for the next major upgrade.

Kind regards,
Ralf