Re: Allowing ALTER TYPE to change storage strategy
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2020-02-29T01:35:33Z
Lists: 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
Commits
-
Allow ALTER TYPE to change some properties of a base type.
- fe30e7ebfa38 13.0 landed