Hi,
As Scott wrote: This is **not** yum's fault. It is your fault actually. Even if you did this upgrade from sources, it would still be broken. PostgreSQL does not guarantee not to change on-disk data structure between development snapshots.
I sort of agree with both sides of the issue - it's not entirely yum's fault, nor is it PostgreSQL's fault, but neither is it the OP's (except for the choice of using a different methodology to what normally works!)
As Konstantin mentioned in another e-mail, PostgreSQL is normally compiled from source and installed into /usr/local/postgres-<version>. Because yum silently upgraded the _existing_ installation, the old version was no longer available to dump out the database.
Had the usual procedure been followed (installed from source) the binaries from the previous version would still have been available in a different directory to be able to dump/reload the database.
My 2p. Regards, Andy -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
