From: | Sašo Gantar <sasog23(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: problem with query |
Date: | 2024-05-20 11:09:00 |
Message-ID: | CAGB0_640Kv4c9Kq5qDNZCNcAxo-_aO=AaKJqBann+iNiU0imWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
what helps is
SET enable_nestloop = off;
query takes less then 2seconds
but it's probably not a good idea to change this flag
On Wed, 15 May 2024 at 13:23, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> On Wed, 15 May 2024 at 21:08, Sašo Gantar <sasog23(at)gmail(dot)com> wrote:
> > this query takes more than 8 seconds,
> > if i remove "AND ((pgn.nspname='servicedesk'))" and test it, it takes <1s
>
> Including the EXPLAIN rather than EXPLAIN (ANALYZE, BUFFERS) isn't
> very useful as there's no way to tell if the planner's estimates were
> accurate or not. Also with EXPLAIN only, we don't know where the time
> was spent in the query.
>
> Running the EXPLAIN with "SET track_io_timing = 1;" would be even more
> useful.
>
> David
>
From | Date | Subject | |
---|---|---|---|
Next Message | milist ujang | 2024-05-20 11:18:30 | Re: signal 11: Segmentation fault ; query constraint list; pg16.3 |
Previous Message | Sašo Gantar | 2024-05-20 11:08:43 | Re: problem with query |