[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[DebianGIS] postgresql in debian



hi martin,

i have successfully built and installed postgresql-8.1 from sid on etch.

all i had to do, is to remove the first and last line from
postgresql-server-dev-8.1.install. they conflict with libpq-dev, which
postgresql-server-dev-8.1 depends on.

i am maintainer of postgis (which tests ok with new 8.1, too), and as
such i am an admiror of your multicluster solution, and i have a few
tips from the part of an inside user:

pg_wrapper has a closed list of programs it is willing to wrap. but this
is a flexibility impediment, since different versions of postgresql may
have various range of utilities. also, contributed packages (as postgis)
may install additional executables in pg_bindir, and they may fail to be
found since they have not been predicted in the list.
i suggest you should activate executables in pg_bindir if, and only if,
they exist in the relevant pg_bindir.

since upstream postgresql still support 7.2, users of this version might
happily move/upgrade to modern debian, if they know their applications
will still work, and they may upgrade at their pace. so, really, what
about having a little 7.2 cluster available, too?

also, part of the programs wrapped by pg_wrapper are scripts, that call
themselves other pg_bindir executables. thus, the script itself may
benefit of having $PGCLUSTER $PGOWNER etc. available, so please
explicitly export them, rather than unexporting them (which you
currently do).

as of migrating to the multicluster environment, this is catastrophic to
users of 3rd party contributed libraries, and it's a pitty: as oposed to
previous one cluster architecture, the running database server is being
preserved, but it is just ;-) moving to another location, where the 3rd
party contributed libraries will naturally not exist.
in my opinion, those libraries should be have links in the new pg_libdir
to the original files, which will be subsequently upgraded by their
maintainers. you should only save a list of these link files, so that
you can safely remove them upon uninstall.

when you make maintainer operations on the existing databases, please
take into consideration there might exist non-connectible (possible
template) databases other than template0, and act on them as required.

best regards,
and many thanks for your very useful work,

alex



Reply to: