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 <draag...@gmail.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 <fmhab...@gmail.com> wrote: >> Any ideas, please? >> >>> On Thu, Sep 13, 2018, 3:49 PM Fd Habash <fmhab...@gmail.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 >>> >>>
