Re: log_planner_stats and prepared statements - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: log_planner_stats and prepared statements
Date
Msg-id 20190417131120.5yx7hkh6taosukml@momjian.us
Whole thread Raw
In response to Re: log_planner_stats and prepared statements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Apr 17, 2019 at 12:04:35AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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@momjian.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 +



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Checksum errors in pg_stat_database
Next
From: Masahiko Sawada
Date:
Subject: Re: New vacuum option to do only freezing