Message-ID: <5f7b22937061ee8cbe0df08930b6ef2c93624095.camel@cybertec.at>
Subject: Re: Correct query for monitor
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: veem v <veema0000@gmail.com>, Ron Johnson <ronljohnsonjr@gmail.com>, 
 pgsql-general <pgsql-general@lists.postgresql.org>
Date: Sat, 27 Sep 2025 08:37:59 +0200
In-Reply-To: <CAB+=1TXm-4bAQBiomkoob6RBO3R7QJo_ZzC+KiFv7rQwgtD_EQ@mail.gmail.com>
References: 
	<CAB+=1TWW4DJwD0XPgud2bTJOuW0HkJ+rU11CL=mU93d4HXwfeA@mail.gmail.com>
	 <CANzqJaALHY3HiyPz64g1iOaNe9aVmzUe_33KpyqZVsnHMS=P_Q@mail.gmail.com>
	 <CAB+=1TXm-4bAQBiomkoob6RBO3R7QJo_ZzC+KiFv7rQwgtD_EQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/5f7b22937061ee8cbe0df08930b6ef2c93624095.camel%40cybertec.at>
Precedence: bulk

On Sat, 2025-09-27 at 01:45 +0530, veem v wrote:
> If we want to identify, what exact query=C2=A0inside=C2=A0a procedure is =
taking a longer time:
> - Using any pg_* views, Is there an easy way to tie the query_id of the p=
rocedure
> with the query_ids of the internal sqls(those are executed within the pro=
cedure)
> to quickly get the culprit sql?

No, you have to read the function body.  Then you can look for the statemen=
ts therein
in pg_stat_statements.

> And say , we got the=C2=A0sql and saw a bad plan and we want to change th=
e plan or attach
> a good plan to that query , is there a possible way to do=C2=A0that in po=
stgres?

No, there isn't.  You can use the pg_hint_plan extension and its query hint=
s to force
a certain execution plan.

Yours,
Laurenz Albe