Re: Peter Eisentraut 2013-07-03 <[email protected]> > Marking only the stable version doesn't sound very reliable. If you > want to guard the data, you have to do it independent of what the > preferred version is. Users of apt.postgresql.org will have even more > complex requirements.
Nod. I was thinking about putting something like ^postgresql-.*$VERSION in the config file when a $VERSION cluster is created, and removing that once the last $VERSION cluster is removed. That would always keep the local databases running, and would also enable cleanup once they got upgraded. The place to put this would be postgresql-$VERSION.postinst, pg_createcluster, and/or the init script for creation, and pg_dropcluster and/or the initscript for removal. (Maybe another call in *.postinst.) Too much magic, too complicated? Or the right way to go? Christoph -- [email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
