From: | Holger Jakobs <holger(at)jakobs(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Related To Query Optimization |
Date: | 2023-05-11 15:11:07 |
Message-ID: | 3c797d81-49e6-e8a2-b1b0-b63cb25901e5@jakobs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Am 11.05.23 um 16:50 schrieb ROHIT SACHDEVA:
>
> Hi Team,
>
> I am facing an issue where one of the queries is taking time in
> production.
> When I put that query in explain, I found many nested loop conditions
> were being used, so just for testing, I disabled the enable_nestloop
> flag for a session, and now the query is running fast.
> I also ran an analyze on every table of that query and also indexing
> is there on required columns.
>
> Tell me where i am wrong and what can be done, as i don't want to
> disable it because, according to me, it's not a good practise.
>
>
> --
> Have a Good day !!!
>
> Regards
> Rohit Sachdeva
I think it's totally impossible to tell without knowing more details.
Please post the CREATE TABLE commands, the number of rows in the tables,
the SELECT command and the output of EXPLAIN.
Kind Regards,
Holger
> --
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
From | Date | Subject | |
---|---|---|---|
Next Message | kaido vaikla | 2023-05-11 15:35:53 | Re: pg_stat_activity query_id |
Previous Message | Holger Jakobs | 2023-05-11 15:09:45 | Re: nextval() on serial using old, existing value on insert? |