Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: avinash varma <avinashvarma443(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
Date: 2019-12-17 16:31:34
Message-ID: 26233.1576600294@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> You've been asked (at least) twice to check size of statistics stored in
> pg_stats. It's really hard to help you when you don't provide important
> information like this.

Apparently we need to be more explicit. What we want to see is

select most_common_vals from pg_stats
where tablename = 'child' and attname = 'id';

select most_common_vals from pg_stats
where tablename = 'core' and attname = 'groupid';

from both databases. (Adjust as necessary if those weren't the
real table and column names.) We probably don't need the specific
array elements, but we do want to know how big those arrays are.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-12-17 17:04:20 Re: weird long time query
Previous Message Arseny Sher 2019-12-17 15:15:42 Re: ERROR: subtransaction logged without previous top-level txn record