Hi Martin,
> ----------------------------------------
> How did you install 9.0? postgresql-common's pg_createcluster usually
> picks the next free port, so in normal setups this "just works", and
> an apt-get install p-9.0 in this situation should end up on port 5433.
> What does "pg_lsclusters" say for you?
Aptitude automatically marked the meta-package "postgresql" as upgradeable and
so installed all 9.0 related packages and upgraded the postgresql-common to
version 111. So maybe wrong order of installing these packages??? The 8.4
remained installed which is definitely correct. All was done automatically, I
just checked the preview, what will it install/upgrade and it was perfectly ok.
I don't have 8.4 anymore, so pg_lsclusters shows only:
9.0 main 5432 online .................
> > I do not remember such behavior while upgrading 8.3 -> 8.4. There was
> > something like auto-switch-to-next-port-available feature.
>
> Yes, and this didn't change. It is possible that the port
> configuration for your 8.4 cluster perhaps changed in a particular way
> which pg_createcluster can't detect? Perhaps you can attach your
> /etc/postgresql/8.4/main/postgresql.conf?
I'm definitely sure both services were configured to the same port number
(5432) - I had to fix that manually to get the 9.0 installed.
Can you try to reproduce the problem? I can also try again...
I also think, a part of the solution generally is to get the postinst script in
the package NOT depend on a successful execution of the service. Of course it
should throw a BIG-FAT-WARNING, that the service was unable to start, but
should not fail with the installation.
Cheers,
Rene
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
