On Wed, 2011-06-29 at 12:34 -0400, Robert Haas wrote: > But now that I'm thinking about this a little more, I'm worried about this > case: > > CREATE TABLE foo AS RANGE('something'::funkytype, 'somethingelse'::funktype); > DROP TYPE funkytype; > > It seems to me that the first statement had better fail, or else the > second one is going to create a hopeless mess (imagine that a new type > comes along and gets the OID of funkytype).
Interesting point. I don't think it's a problem because pseudo-types can't be used that way, so that provides us a mechanism to stop it. But it means that we have to be a little more sure that such values can't persist anywhere. Regards, Jeff Davis -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers