From: | Andy Shellam <andy-lists(at)networkmail(dot)eu> |
---|---|
To: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Yum upgrade of PostgreSQL 8.4 from to rc1 rendered data unusable |
Date: | 2009-06-16 16:46:01 |
Message-ID: | 4A37CC49.7000801@networkmail.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2009-06-16 16:58:53 | Re: Yum upgrade of PostgreSQL 8.4 from to rc1 rendered data unusable |
Previous Message | Steve Crawford | 2009-06-16 15:47:24 | Re: Database Import..Please Help Me |