[Pkg-postgresql-public] Bug#742874: doesn't start correct cluster after upgrade to 9.3

[Wouter Verhelst]

Package: postgresql-9.3
Version: 9.3.4-1
Severity: important

Hi,

Something went wrong during the upgrade of postgresql-9.1 to
postgresql-9.3. I'm not sure exactly what, but the case is currently
that the following has happened:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Naam                               Versie          Architecture Omschrijving
+++-==================================-===============-============-========================================================
ii  postgresql                         9.3+154         all          object-relational SQL database (supported version)
ii  postgresql-9.1                     9.1.12-0wheezy1 amd64        object-relational SQL database, version 9.1 server
ii  postgresql-9.1-debversion          1.0.6-1+b1      amd64        Debian version number type for PostgreSQL
ii  postgresql-9.3                     9.3.4-1         amd64        object-relational SQL database, version 9.3 server
ii  postgresql-9.3-postgis-2.1         2.1.1-5         amd64        Geographic objects support for PostgreSQL 9.3
ii  postgresql-9.3-postgis-scripts     2.1.1-6         all          Geographic objects support for PostgreSQL 9.3 -- scripts
ii  postgresql-client-9.1              9.1.12-0wheezy1 amd64        front-end programs for PostgreSQL 9.1
ii  postgresql-client-9.3              9.3.4-1         amd64        front-end programs for PostgreSQL 9.3
ii  postgresql-client-common           154             all          manager for multiple PostgreSQL client versions
ii  postgresql-common                  154             all          PostgreSQL database-cluster manager

wouter at carillon:~$ sudo service postgresql start
[....] Starting PostgreSQL 9.1 database server: main

this waits a while, and then it fails. Passing the additional "9.3"
argument does nothing.

I'm not sure what exactly is wrong here, and I'm reluctant to throw away
the cluster (even if it doesn't really contain any important data that
can't be recreated)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages postgresql-9.3 depends on:
ii  libc6                  2.18-4
ii  libcomerr2             1.42.9-3
ii  libgssapi-krb5-2       1.12.1+dfsg-1
ii  libkrb5-3              1.12.1+dfsg-1
ii  libldap-2.4-2          2.4.39-1
ii  libpam0g               1.1.8-2
ii  libpq5                 9.3.4-1
ii  libssl1.0.0            1.0.1f-1
ii  libxml2                2.9.1+dfsg1-3
ii  locales                2.18-4
ii  postgresql-client-9.3  9.3.4-1
ii  postgresql-common      154
ii  ssl-cert               1.0.33
ii  tzdata                 2014a-1

postgresql-9.3 recommends no packages.

Versions of packages postgresql-9.3 suggests:
pn  locales-all             <none>
pn  oidentd | ident-server  <none>

-- no debconf information