On 2010/11/08 09:15, Jeff Ross wrote: > On 11/08/10 07:48, Pierre-Emmanuel André wrote: > >On Mon, Nov 08, 2010 at 09:27:27AM -0500, Brandon Mercer wrote: > >>2010/11/8 Pierre-Emmanuel André<p...@raveland.org>: > >>>Hi, > >>> > >>>I've just updated PostgreSQL to it's latest version: 9.0.1. > >>>As usual, a dump/restore is needed for this upgrade. > >>>I wrote a small howto for those who need help: > >>>http://openbsd.raveland.org/ports/postgresql/UPGRADE_HOWTO.txt > >>> > >>>If you want more informations about this version, you can look at > >>>http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.0 > >>> > >>>Please note that: > >>>+ pkg_add will warn you about this upgrade (usefull if you forgot > >>>to dump all your databases) > >>>+ skytools is currently broken. I will commit a new version in a > >>>few days. > >> > >>I thought the 9.x branch had better tools to upgrade from previous > >>versions? Is this just untrue in general or only for OpenBSD's port? > >>Brandon > >> > > > >There is pg_upgrade ( > >http://www.postgresql.org/docs/9.0/static/pgupgrade.html ) > >but you need to have 2 versions installed in the same time (ex: 8.4.5 and > >9.0.1). > >Regards, > > > > I seem to recall seeing somewhere that other OS packagers install the > postgresql binaries into version specific directories--i.e. 8.4 would > have installed into /usr/local/pgsql/84 and then 9.0 would install > into /usr/local/pgsql/90, with the installer symlinking the latest > binary into the $PATH. > > Could the OpenBSD package do something similar?
this means a bunch of additional work handling libraries (and changes in all the ports that use libpq). not impossible, but it's a lot of work.
