| From: | hassan rafi <haassaan(dot)khann(at)gmail(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <rob(at)xzilla(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Seeing high query planning time on Azure Postgres Single Server version 11. |
| Date: | 2024-03-11 06:30:23 |
| Message-ID: | CAMWcn_kjLsi_1NyDvXEJeydAhRYvvUHizpEKwLW4PHY-Eq7n5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks all. Will try upgrading the postgres version.
On Sun, Mar 10, 2024 at 11:44 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
wrote:
> On Sun, Mar 10, 2024 at 1:34 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
> wrote:
>
>>
>> On Sat, Mar 9, 2024 at 1:57 PM hassan rafi <haassaan(dot)khann(at)gmail(dot)com>
>> wrote:
>>
>>> Would upgrading to the latest version of Postgres potentially solve the
>>> issue?
>>>
>>
>> Potentially, yes, but the only one who can answer that for sure is you.
>> Upgrade to 11.22 and re-run the query. Worst case scenario, it runs the
>> same speed but you gained yourself a bunch of bugfixes and CVE resolutions.
>> If the problem persists on 11.22, spin up a Postgres 16, load the data, and
>> test it there.
>>
>
> We have a similar situation with 9.6.24. 14.10 is
> noticeably faster (between 10% and 80%, depending on the query.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2024-03-11 08:38:17 | Re: walsender RAM increases by 500 MB while data is 80 MB |
| Previous Message | Ilya Basin | 2024-03-10 20:51:21 | Re: Query plans not identical for `id in(1,2,3)` and `(id=1 or id=2 or id=3)` |