From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Chris Velevitch" <chris(dot)velevitch(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: create view problem |
Date: | 2006-06-05 14:52:10 |
Message-ID: | 20176.1149519130@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Chris Velevitch" <chris(dot)velevitch(at)gmail(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Witney | 2006-06-05 15:02:20 | Re: does this mean i have a corruption? |
Previous Message | Tom Lane | 2006-06-05 14:45:43 | Re: does this mean i have a corruption? |