Thanks all. Will try upgrading the postgres version. On Sun, Mar 10, 2024 at 11:44 PM Ron Johnson <ronljohnso...@gmail.com> wrote:
> On Sun, Mar 10, 2024 at 1:34 PM Greg Sabino Mullane <htamf...@gmail.com> > wrote: > >> >> On Sat, Mar 9, 2024 at 1:57 PM hassan rafi <haassaan.kh...@gmail.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. > >
