| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "sabrina lal" <sabrina_lal2300(at)hotmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: |
| Date: | 2003-10-13 04:48:18 |
| Message-ID: | 7468.1066020498@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"sabrina lal" <sabrina_lal2300(at)hotmail(dot)com> writes:
> I found out that the debug levels and EXPLAIN command lets you know the
> selection made at each step of the query execution. I wanted to know if
> there was or there can be a way to find out what query paths are considered
> while forming the query execution plan.
Compiling with -DOPTIMIZER_DEBUG provides some visibility into the
process, but I'd be the first to say we could use more. Please feel
free to propose mechanisms for improving this.
regards, tom lane
PS: please use a relevant Subject: line in future pghackers postings.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2003-10-13 05:34:21 | Re: fix for strict-alias warnings |
| Previous Message | Tom Lane | 2003-10-13 04:43:07 | Re: fix for strict-alias warnings |