> I suppose that spirit is quite evident in the documentation.
All kidding aside, the problem that you are having IS recognized as a
weakness with PostgreSQL. This is why some are already working on
solving the problem of in place upgrades. Some time in the future
perhaps > 8.4 this will be a mute point. In the meantime, there are
other workarounds (which of course can be complex) to mitigate this
problem.
> Why make it easy or easily understandable when you can win fanatical
> fans by requiring them to invest months of their time!
I sense your frustration. But it is important to remember that the
PostgreSQL project is largely supported by volunteers. I am sure that
you agree that no one intentionally designs any give task to be more
complicated than necessary. As a side note there are many useful "how
to" articles on the web. Many of these HOWTOs were created by users
(like yourself) that have faced a difficult problem with no apparent
solution. However, after struggling with the problem and then finding
a solution, they document it for all to benefit from. Perhaps some
good with come from overcoming this challenge.
So in the mean time, the best advice is not to rush time upgrade but
take your time to insure that you do it right the first time.
Some useful article that you should consider are:
http://www.depesz.com/index.php/2008/05/05/error-operator-does-not-exist-integer-text-how-to-fix-it/
http://people.planetpostgresql.org/greg/index.php?/archives/136-Upgrading-to-8.3-MediaWiki-lessons-learned.html
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
No comments:
Post a Comment