Simon Bertrang wrote:
Hi,
first, here's an update of postgresql to the next major version, 8.3 [0],
and thus the usual dump/restore procedure is necessary.
Second, there are some more changes that might need your attention:
- tsearch2 has moved to the core distribution, some minor syntax changes,
changed the pg_catalog schema and thus needs some adjustments.
- postgresql-uuid is superseeded by native uuid support but has a
different function naming, so it also needs some minor adjustments.
The single fact that native support allows using NULL values in
foreign key constraints makes uuid usage much easier in a few
situations.
In any case the uuid diff is required, otherwise postgresql pulls in
uuid which pulls in postgresql and so on...
Please test, give feedback and eventually oks.
I want to know first how hard updates of real applications will be
(with stored procedures etc). There are incompatibilities between
8.2 and 8.3 in the area of type conversions e.g.
If an update means a lot of hazzle, then we should consider keeping
both branches in the tree, like we do with python and other stuff.
