Dmitriy Igrishin <dmitigr@xxxxxxxxx> writes: > 2013/4/5 Tom Lane <tgl@xxxxxxxxxxxxx> >> We do not generally forbid ALTER on extension members. During >> development for instance a quick ALTER can be a whole lot more >> convenient than dropping and reloading the whole extension. > Debatable, because in practice during development it's often better to > recreate the whole database which takes seconds. [ shrug... ] Maybe in *your* usage that's invariably true, but other people do things differently. A typical case where it's important not to force this is where you're working on a datatype extension, and dropping the extension would require dropping all your tables containing test data. If you're doing performance testing you've probably got enough test data that a drop and reload will be costly. Anyway, the established design is that the extension mechanism per se is not meant to prevent altering an extension's member objects, only dropping them altogether. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
