From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PAscal L <legrand_legrand(at)hotmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: simple query profile and tracing API |
Date: | 2018-11-14 13:09:58 |
Message-ID: | CAFj8pRCOpiQAOEDS+=mPHgKn5PckgAoaawZAqoCjddcu8ppXTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
st 14. 11. 2018 v 14:06 odesílatel legrand legrand <
legrand_legrand(at)hotmail(dot)com> napsal:
> Pavel Stehule wrote
> > út 13. 11. 2018 v 20:38 odesílatel Tomas Vondra <
>
> > tomas.vondra@
>
> >> napsal:
> >
> > My idea is very simple.
> >
> > 1. continual collect of data - planning start, execution start, waiting
> > start, waiting end, query end
> >
> > 2. run a some callback function after query is finished. Collected data
> > will be passed there.
> >
> > I think so anybody can do some different with these data. Sometimes only
> > sum can be ok, sometimes you need to increment some sorted counts,
> > sometimes you need to store these data for median or percentil
> > calculation.
> >
> > I think so it can be very simple and fast, because you should to work
> with
> > just one metrics vector.
>
> the same idea was already proposed for planning time in pg_stat_statements
> by Thomas
>
> https://www.postgresql-archive.org/Planning-counters-in-pg-stat-statements-tt5990933.html#a6002416
Should not be original every time :)
Regards
Pavel
>
> Regards
> PAscal
>
>
>
>
> --
> Sent from:
> http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Darafei Komяpa Praliaskouski | 2018-11-14 13:59:02 | Re: Changing SQL Inlining Behaviour (or...?) |
Previous Message | legrand legrand | 2018-11-14 13:05:52 | Re: proposal: simple query profile and tracing API |