>>>>> "Tom" == Tom Lane <t...@sss.pgh.pa.us> writes:
>> I've wondered for a while whether this wouldn't have been better >> handled as: >> create view qwr(colnames...) as select null::type1, null::type2, ...; >> /* ... */ >> create or replace view qwr as ...; Tom> Yeah, possibly. The existing pg_dump coding dates from before we Tom> had CREATE OR REPLACE VIEW. As it happens it does not; the issue came up originally because of a hack I came up with, and I've never used any pg version so old it didn't have CREATE OR REPLACE VIEW. Nor does it look like the change was ever backpatched (or at least not that far). http://www.postgresql.org/message-id/20986.1102296...@sss.pgh.pa.us Of course, at the time I myself didn't think of using a view rather than a table for the initial creation; I was focused on rules because that was the only way to get updateable views then. So arguably it is at least partly my fault. Tom> But we'll have to live with pg_dump files that do this for the Tom> indefinite future, so I agree some fix is needed on the backend Tom> side. Certainly. -- Andrew (irc:RhodiumToad) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
