| From: | Bruce Momjian <bruce(at)momjian(dot)us> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: log_planner_stats and prepared statements | 
| Date: | 2019-04-17 13:11:20 | 
| Message-ID: | 20190417131120.5yx7hkh6taosukml@momjian.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Wed, Apr 17, 2019 at 12:04:35AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I have found that log_planner_stats only outputs stats until the generic
> > plan is chosen.  For example, if you run the following commands:
> 
> Uh, well, the planner doesn't get run after that point ...
Yes, that was my analysis too, but EXPLAIN still prints a planner line,
with a duration:
	 Planning Time: 0.674 ms
	 Planning Time: 0.240 ms
	 Planning Time: 0.186 ms
	 Planning Time: 0.158 ms
	 Planning Time: 0.159 ms
	 Planning Time: 0.169 ms
-->	 Planning Time: 0.012 ms
Is that consistent? I just don't know. What is that line measuring?
-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2019-04-17 13:38:11 | Re: New vacuum option to do only freezing | 
| Previous Message | Julien Rouhaud | 2019-04-17 13:07:04 | Re: Checksum errors in pg_stat_database |