From: | Fred Habash <fmhabash(at)gmail(dot)com> |
---|---|
To: | Patrick Molgaard <draaglom(at)gmail(dot)com> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: How Do You Associate a Query With its Invoking Procedure? |
Date: | 2018-09-16 21:53:58 |
Message-ID: | E96A3EB0-1CFD-464C-9ED5-CC6F90C82DD6@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
All great ideas.
I was thinking something similar to some other RDBMS engines where SQL is automatically tied to the invoking PROGRAM_ID with zero setup on the client side. I thought there could be something similar in PG somewhere in the catalog.
As always, great support. This level of support helps a lot in our migration to Postgres.
————-
Thank you.
> On Sep 15, 2018, at 5:24 AM, Patrick Molgaard <draaglom(at)gmail(dot)com> wrote:
>
> You might find application-level tracing a more practical answer - e.g. check out Datadog APM for a (commercial) plug and play approach or Jaeger for a self-hostable option.
>
> Patrick
>> On Fri, Sep 14, 2018 at 4:38 PM Fred Habash <fmhabash(at)gmail(dot)com> wrote:
>> Any ideas, please?
>>
>>> On Thu, Sep 13, 2018, 3:49 PM Fd Habash <fmhabash(at)gmail(dot)com> wrote:
>>> In API function may invoke 10 queries. Ideally, I would like to know what queries are invoked by it and how long each took.
>>>
>>>
>>>
>>> I’m using pg_stat_statement. I can see the API function statement, but how do I deterministically identify all queries invoked by it?
>>>
>>>
>>>
>>>
>>>
>>> ----------------
>>> Thank you
>>>
>>>
From | Date | Subject | |
---|---|---|---|
Next Message | still Learner | 2018-09-17 12:38:33 | Big image tables maintenance |
Previous Message | Rory Campbell-Lange | 2018-09-16 12:23:36 | Advice on machine specs for growth |