On Sat, 2025-09-27 at 01:45 +0530, veem v wrote:
> 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
On Fri, Sep 26, 2025 at 4:15 PM veem v 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
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(thos
Hello,
We want to have monitoring on three things 1) If the database restarted or
went down in the last few hours? 2)If the connections are high 3) High
tablespace growth . Want to understand , if we can utilize below queries
for the same or any flaws in this strategy?
1)SELECT
CASE
WHEN now
