Your message dated Sat, 8 Dec 2018 20:47:28 +0100
with message-id <20181208194728.ga30...@msg.df7cb.de>
and subject line Re: [Pkg-postgresql-public] Bug#915965: postgresql-11: 
postgresql listens on non-default port number 5433
has caused the Debian Bug report #915965,
regarding postgresql-11: postgresql listens on non-default port number 5433
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
915965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-11
Version: 11.1-1+b2
Severity: important

Dear Maintainer,

after some recent upgrade (within the last couple months), postgresql seemingly
switched from listening on port 5432 to listening on port 5433.  I only found
out because an application that used to work just fine suddenly stopped working
and complained it could not find the unix domain socket it expected.

I do not know why it now says "port = 5433" in my
/etc/postgresql/11/main/postgresql.conf, but I know for sure that I did not
change this configuration.  According to etckeeper, this happened when I
upgraded from postgresql-10 to postgresql-11, which happened automatically via
dist-upgrade.  (I had to manually uninstall postgresql-10 afterwards, but did
not think much about that.)

Debian not using the default port means that all sorts of applications and
tutorials will just not work, and it can take a while for people not deeply
familiar with postgres to figure out what is going on.  And either way, changing
the DB port without administrator intervention is claerly a bug.  DB upgrades
should not have side-effects like changing the DB port.

Kind regards,
Ralf

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages postgresql-11 depends on:
ii  libc6                 2.27-8
ii  libgcc1               1:8.2.0-9
ii  libgssapi-krb5-2      1.16.1-1
ii  libicu63              63.1-4
ii  libldap-2.4-2         2.4.46+dfsg-5+b1
ii  libllvm7              1:7-6
ii  libpam0g              1.1.8-3.8
ii  libpq5                11.1-1+b2
ii  libselinux1           2.8-1+b1
ii  libssl1.1             1.1.1a-1
ii  libstdc++6            8.2.0-9
ii  libsystemd0           239-13
ii  libuuid1              2.32.1-0.1
ii  libxml2               2.9.4+dfsg1-7+b2
ii  libxslt1.1            1.1.32-2
ii  locales               2.27-8
ii  postgresql-client-11  11.1-1+b2
ii  postgresql-common     197
ii  ssl-cert              1.0.39
ii  tzdata                2018g-1
ii  zlib1g                1:1.2.11.dfsg-1

Versions of packages postgresql-11 recommends:
ii  sysstat  12.0.1-1

Versions of packages postgresql-11 suggests:
pn  locales-all  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Re: Ralf Jung 2018-12-08 
<154429452196.14297.5405526035587989611.reportbug@r-thinktop>
> DB upgrades should not have side-effects like changing the DB port.

Hi Ralf,

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.

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

Christoph

--- End Message ---
_______________________________________________
pkg-postgresql-public mailing list
pkg-postgresql-public@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-postgresql-public

Reply via email to