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".
