"Chris Velevitch" <[EMAIL PROTECTED]> writes:
> But, wouldn't you want to see the execution plan for the select
> statement that appears in the create?
Then give the EXPLAIN the select statement that appears in the create.
Logically, EXPLAIN of a DDL statement would tell you about the costs
of performing the catalog modifications involved in the DDL statement.
Which wouldn't have anything to do with what you request above. I don't
believe that CREATE VIEW ever bothers to form a plan for the view query
at all --- it just stuffs the parse tree into the catalogs.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
