Package: postgresql-common Version: 278 Severity: normal After successful conversion the upgrade process starts a progressive ANALYZE. At that point the database is already running. Failing the ANALYZE the upgrade process removes the database which was already opened for use. This is extremely unfortunate, guess why. (It can happen when the analyze runs long, the upgrade "forgets" to copy conf.d and the admin copies conf.d over and restarts the db, since analyze would run forever.)
(At that point the old database is hardlinked but seems it's not possible to start it as new, since some files were not touched. It cannot be re-upgraded either, it would be bad anyway since the db was already running and possibly changed.)
