Pg_stat_activity

From: Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Pg_stat_activity
Date: 2025-02-16 00:31:15
Message-ID: CAJk5AtYs9NynsNwkBumh1C-_eYrkBwLWNzhHhwmTqKuRsE5WJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

If I see a sudden connection spike (say once in 2 months). What are the
steps I need to follow as a dba?

Check idle and kill? Check of stat activity for active queries? How do I
ensure how much time is long running query? Blocking queries? How much of
blocking time is considered to be dangerous? Locks - should we conclude
anything from wait event and wait event type ?

All these won't help nd have to look into pgbadger?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-02-16 01:02:05 Re: Pg_stat_activity
Previous Message Jeff Davis 2025-02-15 22:42:54 Re: Decision by Monday: PQescapeString() vs. encoding violation