On 2017-04-19 16:43:07 -0700, Michael Malis wrote: > > The profile seems to confirm that this is largely due to cache misses. > > Can you elaborate? Cache misses of what? Why is the planning time so > variable?
Postgres uses caches for a lot of metadata of tables, indexes, ... Some actions, like vacuum, DDL, table size changes trigger cache invalidations for other backends so the caches stay coherent. What you're likely seeing is that the cached cases are quick enough, and that the slow plan cycles are when the cache has been invalidated. - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
