On Mon, 28 Jul 2014, Christoph Berg wrote: > > So, how d̲o̲ I recover from this without making things worse, now? > > You can just start the old cluster again. (The only thing that could > be changed there are the port number and start.conf, but judging from > the errors you got it died way before that point.)
OK, thank you. Starting needed me to *stop* the old cluster (using the init script) in the first place, judging from “ps ax” output… apparently, there were several Akonadi sessions still open. I could then successfully upgrade the cluster. The bug remains: pg_upgradecluster should not fail to upgrade the cluster (it’s called as root, so it could just use the same mechanism which the init script uses to stop it), and must not bring the DB into such an inconsistent state. Apparently, this is nothing new, but my (and others’) use of psql as KDE backend (instead of a non-database) will trigger it more often now. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg _______________________________________________ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public