From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-performance@lists.postgresql.org
Subject: Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle
Date: Fri, 8 Oct 2021 18:07:17 +0200
Message-ID: <ed3d7396-157e-7ed5-4344-0bdd5799ac6c@gmx.net> (raw)
In-Reply-To: <20211008154023.GC31533@momjian.us>
References: <CAMzkAgGAwh=vsUmtEOC-57GhbFo4eh_B7gJCWMqH4yR7hHJjgA@mail.gmail.com>
<CAH2-Wzn-+=aYrMw4pHbV7yYVyRYskJkNLaV6HeHj94oyKJiRKA@mail.gmail.com>
<efbd4d1a-48d5-99ac-549f-5e3f37812273@ardentperf.com>
<4d9e6ac5-5b13-84fe-74b5-07421501318e@gmail.com>
<20211008152132.GB31533@momjian.us>
<738e0157-da3f-01aa-4e43-2b6e3c08ecca@gmx.net>
<20211008154023.GC31533@momjian.us>
Bruce Momjian schrieb am 08.10.2021 um 17:40:
>> I guess everyone will use that information in a different way.
>>
>> We typically use the AWR reports as a post-mortem analysis tool if
>> something goes wrong in our application (=customer specific projects)
>>
>> E.g. if there was a slowdown "last monday" or "saving something took minutes yesterday morning",
>> then we usually request an AWR report from the time span in question. Quite frequently
>> this already reveals the culprit. If not, we ask them to poke in more detail into v$session_history.
>>
>> So in our case it's not really used for active monitoring, but for
>> finding the root cause after the fact.
>>
>> I don't know how representative this usage is though.
>
> OK, that's a good usecase, and something that certainly would apply to
> Postgres. Don't you often need more than just wait events to find the
> cause, like system memory usage, total I/O, etc?
Yes, the AWR report contains that information as well. e.g. sorts that spilled
to disk, shared memory at the start and end, top 10 statements sorted by
total time, individual time, I/O, number of executions, segments (tables)
that received the highest I/O (read and write) and so on.
It's really huge.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: shammat@gmx.net, pgsql-performance@lists.postgresql.org
Subject: Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle
In-Reply-To: <ed3d7396-157e-7ed5-4344-0bdd5799ac6c@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox