Public bug reported: Binary package hint: postgresql-8.4
fat...@nikko:~$ lsb_release -rd Description: Ubuntu 9.04 Release: 9.04 Package: postgresql-8.3/postgresql-8.4 Here is my scenario: I have a Jabber server using Postgres as a backend. Everything was working fine. One day I did a "sudo aptitude update && sudo aptitude safe-upgrade" and forgot about it. The next day I couldn't log in to my Jabber server. Took me a few days but eventually I figured out it was Postgres. I was unable to log in to the database itself using the usual usernames and passwords. This thread on Ubuntu Forums has the details: http://ubuntuforums.org/showthread.php?t=1380408 What I expected to happen: 8.3 quietly becomes 8.4 and continues working. Port numbers do not change. A new, blank database is *not* installed, instead the old one remains. Database users can still log in, as before. If something's going to break, it does so loudly and unambiguously. If something breaks, a note appears in a log file somewhere. What actually happened: Seems Postgres tried to install 8.4 side-by-side with 8.3. Ok, fine, but if it's going to do that, why does it then disable 8.3 and break my client daemons? Isn't something wrong here? Workaround: $ sudo aptitude remove postgresql-8.4 $ sudo aptitude install postgresql-8.3 This restored my database. Thanks for reading. ** Affects: postgresql-8.4 (Ubuntu) Importance: Undecided Status: New -- upgrade makes database inaccessible https://bugs.launchpad.net/bugs/538995 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
