From: | Thomas Güttler <guettliml(at)thomas-guettler(dot)de> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Automated bottleneck detection |
Date: | 2018-07-26 11:27:38 |
Message-ID: | 14b51a31-df17-62ab-1b00-778cce29e57d@thomas-guettler.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
This sound good. Looks like an automated bootleneck detection
could be possible with pg_wait_sampling.
Regards,
Thomas
Am 25.07.2018 um 12:25 schrieb Julien Rouhaud:
> On Wed, Jul 25, 2018 at 11:14 AM, Thomas Güttler
> <guettliml(at)thomas-guettler(dot)de> wrote:
>>
>> AFAIK powa is based on pg_stat_statements not on statistical samples.
>> But maye I am wrong.
>
> Indeed, it's based on pg_stat_statements, but other extensions are
> supported too. Since pg_stat_statements already provides cumulated
> counters, there's no need to do sampling. But if you're interested in
> wait events information for instance, it supports (in development
> version) pg_wait_sampling extension, which does sampling to provide
> efficient and informative informations.
>
--
Thomas Guettler http://www.thomas-guettler.de/
I am looking for feedback: https://github.com/guettli/programming-guidelines
From | Date | Subject | |
---|---|---|---|
Next Message | MichaelDBA | 2018-07-26 12:05:10 | Re: Automated bottleneck detection |
Previous Message | Julien Rouhaud | 2018-07-25 10:25:49 | Re: Profile what the production server is doing |