and a dump that orders the two views arbitrarily. We can certainly add code to do something different, but are there any real-world cases where this is needed? The above example seems more than slightly made-up. The views aren't actually functional anyway (trying to use either would result in an "infinite recursion" error). Can you show me a non-broken situation where pg_dump needs to resort to view shells?
Well then shouldn't we just ban you from creating a view that creates a circular dependency?
Thinks... How about if the views were using each others 'table type' to do something? Although you cannot change the return type definition can you?
Hmmm.
Also shouldn't we really separate out the 'can modify catalogs manually' privilege from the 'superuser' privilege?
See pg_shadow.usecatupd. This could stand to be better supported maybe (like with ALTER USER support)?
Sounds like this should be a TODO...
Chris
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
