| From: | "Vladimir Sitnikov" <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: contrib/pg_stat_statements 1202 |
| Date: | 2008-12-09 16:51:44 |
| Message-ID: | 1d709ecc0812090851p2d6fa1a7uee3908ccc4775d8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> I'm not sure what the best way is though. I don't think continuing to
> add keywords between EXPLAIN and the start of the query is very
> scalable. Putting parentheses around the option list seems like it
> might eliminate a lot of grammar headaches:
Do you think it is required to invent special grammar just for presentation
purposes?
I guess database should not deal with presentation. Provided "explain"
retuns table, it is up to the client to do the formatting. I do not believe
it makes sense creating several different explain outputs, and redo all the
work in 8.5.
It still could make sense having several options for "explain" if that would
result in *different instrumentation *(e.g. "explain" vs "explain analyze").
Regards,
Vladimir Sitnikov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2008-12-09 16:52:56 | Re: cvs head initdb hangs on unixware |
| Previous Message | ohp | 2008-12-09 16:47:47 | Re: cvs head initdb hangs on unixware |