Tom Lane-2 wrote > Or we could add them into > just the first planning-time printout, though that might also be > misleading.
If you are going to show a number for these steps, which seems like a good idea, then this seems like a reasonable option in the face of this situation. Basically two options: 1. Query overhead timing detailed separately 2. Query overhead included with first plans' planning time An explain option: (OVERHEAD '[off?|detail|first]') would then give the user the ability to choose between the two (not sure if off is worthwhile but worth at least rejecting explicitly). David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/So-why-is-EXPLAIN-printing-only-plan-time-tp5801663p5801674.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
