| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: TODO |
| Date: | 2012-08-23 19:21:25 |
| Message-ID: | 20120823192125.GC5971@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 21, 2012 at 12:16:11PM +0900, Tatsuo Ishii wrote:
> I found this in https://wiki.postgresql.org/wiki/Todo :
>
> Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
>
> What does this actually mean?
>
> Add GUC switch to enable optimizer debug on/off?
> More fancy/useful info should be printed?
> If so, what kind of information is required?
Well, right now, OPTIMIZER_DEBUG lets you see what plans were considered
and removed. I was thinking that information should be available
without a special compiled binary.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-08-23 19:48:37 | Re: default_isolation_level='serializable' crashes on Windows |
| Previous Message | Bruce Momjian | 2012-08-23 19:19:36 | Re: Large number of open(2) calls with bulk INSERT into empty table |