> Why don't you run the backup in pgsql's preinst? > If pgsql conflicts with postgres95, its preinst will be executed > before unpacking pgsql, and before postgres95 is removed. > (Debian packaging manual, v 1.4.0.19, section 6.3) > > Another comment, why is it called "pgsql"? Wouldn't it be less cryptic > to use the long name "postgresql"? If you can do it this way - I'd go for it. With PostgreSQL, it's going to be important to figure out how to dump and restore between upgrades. The transition from 1.09 to 6.0 required one, and so did the transition from 6.0 to 6.1. I don't think the transistion from 6.1 to 6.1.1 needed one, however. This situation will probably arise again when 6.2 comes out. I think the preinst stuff might work. The packaging manual has all sorts of details on how the scripts are called (and in what order). It's pretty complex - I haven't spent the time to figure out how it works. Cheers, - Jim
Attachment:
pgp2gmK3ZtXvr.pgp
Description: PGP signature