From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Jan Wieck <jan(at)wi3ck(dot)info> |
Cc: | Tiffany Thang <tiffanythang(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Profiling a function call |
Date: | 2023-05-21 11:42:50 |
Message-ID: | CAFj8pRDAH2Fi-zrtVz_grhT6029SHc4+8Ui2SbqdLa=MFiab9g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
ne 21. 5. 2023 v 13:30 odesílatel Jan Wieck <jan(at)wi3ck(dot)info> napsal:
> On 5/20/23 00:36, Tiffany Thang wrote:
> > Hi,
> > I have a function that has been executing for a long time and not
> > returning any results. Wait event=NULL so it seems like it is still
> > executing and not waiting on any specific resources. Is there a way to
> > profile the function call to get an idea of what it is currently
> > executing within the function? All I could find in pg_stat_activity is
> > the function is running. I want to know what query/transaction within
> > the function is running. Is there a way to obtain that information?
>
> This may give you some idea. I haven't touched or used it in many years,
> but it might get you started:
>
> https://github.com/wieck/plbacktrace
plpgsql_check has integrated tracer
https://github.com/okbob/plpgsql_check#tracer
Regards
Pavel
>
>
>
> Best Regards, Jan
>
> >
> > PostgreSQL 15.2 on Linux.
> >
> > Thanks.
> >
> > Tiff
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Lissner | 2023-05-21 14:56:00 | Re: Trying to understand a failed upgrade in AWS RDS |
Previous Message | Jan Wieck | 2023-05-21 11:27:47 | Re: Profiling a function call |