| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: UPGRADE TO PG11 CAUSED DEGREDATION IN PERFORMANCE |
| Date: | 2019-09-03 17:34:26 |
| Message-ID: | CAHyXU0z7QLL=m9Am+tZUriJGfQJfUU-pTVO7WouyFJtqxBzGew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, Aug 18, 2019 at 1:57 AM Mariel Cherkassky
<mariel(dot)cherkassky(at)gmail(dot)com> wrote:
>
> Hey,
> I upgraded my pg9.6 cluster to pg11.2.
> As it seems after the upgrade the duration of the same flow in my application raised from 13 minutes to 19 minutes.
>
> The test I did :
> 1.reset pg_stat_statements
> 2.run the applicative flow
> 3.collect everything from pg_stat_statements
>
> I did this test on the env before the upgrade and after the upgrade. I took the sum of the total_time in pg_stat_statements and sumed it up.
Since you have performance data, do you see any trends? For example,
is it generalized performance issues or are there specific queries
that have degraded? We would need more specific detail before being
able to give better advice on how to fix performance issue.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Kharin | 2019-09-03 17:47:42 | Incorrect choice of Nested Loop for a skewed distribution |
| Previous Message | Barbu Paul - Gheorghe | 2019-09-03 12:41:33 | Re: Erratically behaving query needs optimization |