| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: implement EXPLAIN EXECUTE |
| Date: | 2003-01-12 19:31:19 |
| Message-ID: | 4077.1042399879@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Neil Conway <neilc(at)samurai(dot)com> writes:
> This patch implements EXPLAIN EXECUTE, including documentation updates.
This seems like quite a messy way to do things. Why not just make the
grammar
ExplainStmt:
EXPLAIN opt_analyze opt_verbose OptimizableStmt
| EXPLAIN opt_analyze opt_verbose ExecuteStmt
where ExplainStmt.query can point to either an optimizable statement
or an ExecuteStmt.
Then you'd not need one single change (I think) in parsenodes.h nor
analyze.c, nor need to expose subroutines of explain.c to outside.
Instead, prepare.c would have to expose a function to fetch the plan
tree for a prepared query, but that seems a reasonable thing to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-01-12 20:26:32 | targetlist functions part 1 (was [HACKERS] targetlist functions proposals) |
| Previous Message | Neil Conway | 2003-01-12 17:04:07 | Re: pg_dump a specific schema |