Robert Haas <robertmh...@gmail.com> writes: > On Sep 10, 2011, at 11:26 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> (IOW, rather than "fix" this I'd prefer to rip out the code altogether. >> But maybe we should wait a couple more years for that.)
> IIRC, it's not dead code. I think you can still generate such a dump if you > use CREATE OR REPLACE VIEW to manufacture a pair of mutually recursive views. Oh, yeah, I'd forgotten about that. In general that's pg_dump's strategy for breaking a circular dependency loop that involves a view. > Now we should probably disallow that, but we currently don't. Losing that particular case isn't problematic, but I'm not sure that that's the only possible circularity involving a view. One idea that comes to mind is create table foo (list-of-columns); create function foofunc () returns setof foo as ...; create rule .... as select * from foofunc(); This only saves somebody from citing the list of column types twice, so maybe we could blow off this case too; but who's to say there are not more-useful cases that would create circularities? regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs