On Tuesday 31 December 2002 22:41, Tony Ziolkowski wrote:
> SO what's the solution? I have an unworking postgresql.
You can try to downgrade to the previous version using 'rpm -U --oldpackage'
The Red Hat 8 release notes very explicitly caution against blind upgrades of
PostgreSQL. A dump should be done _before_ the OS is upgraded. Then you are
supposed to restore from the dump after the upgrade. This has been
documented in the release notes for Red Hat since at least 7.0.
PostgreSQL major version (7.1 to 7.2 is a major version change) upgrades
_always_ involve dumping the database, initdb'ing a new database, and
restoring the database after upgrade.
I sympathize with you; however, due to the nature of PostgreSQL it is very
difficult to facilitate seamless upgrades. Ask on the pgsql-hackers list
about dumpless upgrading for more edification. 'The nature of PostgreSQL'
above refers to its extreme extensibility and the advanced features that
require system catalog changes -- which are the driver behind the
dump/initdb/restore cycle.
As to the out-of-sync README.rpm-dist -- complain to Red Hat for shipping
their packages without programs referred to in the documentation.
Although you didn't mention rh-dump.sh, which is what the README.rpm-dist
documentation file specifically recommends instead of postgresql-dump.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
