On Dec 11, 2010, at 12:09 PM, Dimitri Fontaine wrote: > Yeah that works, as soon as VVV is the version we upgrade from. > > That said, we need to find a way to lighten the process for extensions > where it's easy to have a single script to support upgrade from more > than once past release. > > What about having the following keys supported in the control file: > > upgrade_<version> = 'script.version.sql' > upgrade_all = 'script.sql'
Why not just use an upgrade script naming convention? Think: Convention over configuration. > Where the version here is the version you're upgrading *from* (to is > known and static when you distribute the files after all), and where > upgrade_all is applied last no matter what got applied before. > > Also, do we want a subdirectory per extension to host all those files? How are things currently arranged? Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
