| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | avinash varma <avinashvarma443(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 12:07:51 |
| Message-ID: | 20191217120751.34fmwkshfanjqws2@development |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 17, 2019 at 05:04:18PM +0530, avinash varma wrote:
>>> b) can you compare size of databases, indexes?
>I used the same backup to restore on V10 and V11 . So the no: of indexes
>and size of databases are same.
>
>One observation is that after pg_restore, we are doing vacuum full analyze
>on both V10 and V11.
>
>This is causing the slowness on V11 . Before vacuum analyze , same query is
>performing well on V11.
>
>Is there any changes in the analyze script in V11 when compared to V10.
>
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.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-12-17 12:50:35 | Re: Memory leak (possibly connected to postgis) leading to server crash |
| Previous Message | Roman Cervenak | 2019-12-17 11:51:27 | Re: Memory leak (possibly connected to postgis) leading to server crash |