Comment 9 for bug 871893

From comment #6
>> The problem is quite simple: while upgrading, postgres-8.4 is replaced by postgres-9.1.
>
> No, it's not. 9.1 gets installed in addition.

Sometimes yes, sometimes no. In case of the server in question postgres-8.4 was removed, only the configuration files and databases remained. On an other system postgres-8.4 stood in place, but wasn't started after rebooting. On my third system after upgrading both servers ran. Postgres-8.4 on the standard port, Postgres-9.1 on a port one higher than the standard.

>> The migration described on the postgres project site are not working for Ubuntu:
>
> On upgrade you should have gotten a debconf note that
> describes how to do the upgrade. Please have a look at
> /usr/share/doc/postgresql-common/README.Debian.gz.

Yes, the note is printed. But on a window 132x43 it takes half a second and it is scrolled out of sight. Looking through the apt-logs doesn't really help. It is to easy to overlook such a note. The best I bet would be to pipe notes like that to an extra file, displayed after the upgrade terminates, not forcing one to sit and watch the screen awaiting something important scrolling by.

> If you want to use pg_upgrade, you can install libpq-dev to get pg_config.
>
> I suppose everything is alright on your system, but to verify
> I still need the answers to my questions in comment 2. Thanks!

The only thing not OK at now is duplicate client entries warned about by bacula.