On Fri, Jan 20, 2012 at 3:33 PM, Daniel Farina <dan...@heroku.com> wrote: > On Fri, Jan 20, 2012 at 2:48 PM, Heikki Linnakangas > <heikki.linnakan...@enterprisedb.com> wrote: >> Even if you give the version number in the CREATE EXTENSION command, it's by >> convention that people actually maintain a sane versioning policy. If people >> don't take version management seriously, you will quickly end up with five >> different versions of an extension, all with version number 0.1. > > Projects are taking it seriously, and invest a lot of effort in it. > There is no shortage of schema versioning frameworks, of varying > levels of maturity....but some are quite complete by the standards of > their users. However, there is little knowledge shared between them, > and the no database gives them much support, so idiosyncrasy becomes > inevitable.
Speak of the devil. Someone just posted use of extension versioning to manage schemas (using the existing plain-old-files mechanism): http://philsorber.blogspot.com/2012/01/deploy-schemata-like-boss.html He also links to a -hackers post Dimitri wrote last December. A few anecdotes does not constitute evidence, but it does look like some people pay attention to any additional versioning foothold they can get. -- fdr -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
