public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Correct query for monitor
Date: Fri, 26 Sep 2025 19:00:13 -0400
Message-ID: <CANzqJaCWEZv1VomWQh-rqYcgGobnqqF2cVEabcihBzPuXhBXFA@mail.gmail.com> (raw)
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>
On Fri, Sep 26, 2025 at 4:15 PM veem v <[email protected]> wrote:
> Thank you so much for the quick response. I have a follow up question on
> this as below,
>
> If we want to identify, what exact query inside a procedure is taking a
> longer time:- Using any pg_* views, Is there an easy way to tie the
> query_id of the procedure with the query_ids of the internal sqls(those are
> executed within the procedure) to quickly get the culprit sql?
>
Are there queries inside a cursor loop?
> And say , we got the sql and saw a bad plan and we want to change the plan
> or attach a good plan to that query , is there a possible way to do that in
> postgres?
>
>>
PG does not support hints or "attaching plans to queries".
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Correct query for monitor
In-Reply-To: <CANzqJaCWEZv1VomWQh-rqYcgGobnqqF2cVEabcihBzPuXhBXFA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox