From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Bug or feature? (The constraint of the domain of extension can be dropped...) |
Date: | 2013-04-05 14:04:06 |
Message-ID: | 3261.1365170646@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dmitriy Igrishin <dmitigr(at)gmail(dot)com> writes:
> According to
> http://www.postgresql.org/docs/9.2/static/extend-extensions.html
> "PostgreSQL will not let you drop an individual object contained in an
> extension, except by dropping the whole extension."
> But this rule does not apply to domain constraints, i.e. it is not possible
> to drop domain of some extenstion but it is possible to drop any or all of
> its constraints. (And in fact drop it.)
> I am consider this is a bug. Don't you?
No. The domain is a member of the extension, its properties are not.
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.
Whether it's a good idea to ALTER extension member objects in production
is a different question. Typically you'd install them as owned by
somebody with sense enough not to do that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2013-04-05 15:03:36 | Re: Oracle to PostgreSQL transition? |
Previous Message | Andres Freund | 2013-04-05 14:03:48 | Re: how to completely disable toasted table in postgresql and best practices to follow |