From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: AWS RDS "sessions" and pg_stat_activity |
Date: | 2023-06-21 16:32:38 |
Message-ID: | CAOC+FBWQL9W+GnasCN+1DX7J+BYEO4kH9Y65Z+o=FssMO2bpbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Their use of "sessions" is everywhere. AAS (average active session count)
and all over the insights, including the activity bar. I'm just trying to
map those back to exact things I can query myself from pg_stat_activity.
Little bit on it here
https://aws.amazon.com/blogs/database/analyzing-amazon-rds-database-workload-with-performance-insights/
On Wed, Jun 21, 2023 at 9:29 AM Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Wed, Jun 21, 2023 at 12:06 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
> wrote:
>
>> Just trying to get my head firmly around the RDS session number and
>> associated performance/saturation. It says a session is any request waiting
>> on a response from the server, so I am wondering if that's equivalent to
>> selecting all from pg_stat_activity where state is active, and this would
>> include all concurrent parallel workers, maintenance stuff, etc.
>>
>
> If you are referring to something in the RDS documentation or monitoring,
> could you provide a link to it, or an excerpt of it?
>
> Cheers,
>
> Jeff
>
>>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Cary Huang | 2023-06-21 17:18:23 | Re: SSL cert "not initialized" error with logical replication with 13.11 |
Previous Message | Jeff Janes | 2023-06-21 16:29:02 | Re: AWS RDS "sessions" and pg_stat_activity |