Re: Allowing ALTER TYPE to change storage strategy
От | Tom Lane |
---|---|
Тема | Re: Allowing ALTER TYPE to change storage strategy |
Дата | |
Msg-id | 9226.1582940133@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Allowing ALTER TYPE to change storage strategy (Tomas Vondra <tomas.vondra@2ndquadrant.com>) |
Ответы |
Re: Allowing ALTER TYPE to change storage strategy
Re: Allowing ALTER TYPE to change storage strategy |
Список | pgsql-hackers |
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes: > I think we might check if there are any attributes with the given data > type, and allow the change if there are none. That would still allow the > change when the type is used only for things like function parameters > etc. But we'd also have to check for domains (recursively). Still has race conditions. > One thing I haven't mentioned in the original message is CASCADE. It > seems useful to optionally change storage for all attributes with the > given data type. But I'm not sure it's actually a good idea, and the > amount of code seems non-trivial (it'd have to copy quite a bit of code > from ALTER TABLE). You'd need a moderately strong lock on each such table, which means there'd be serious deadlock hazards. I'm dubious that it's worth troubling with. regards, tom lane
В списке pgsql-hackers по дате отправления: