| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Pg_stat_activity |
| Date: | 2025-02-16 01:02:05 |
| Message-ID: | CAKFQuwZh6YYC3dsiaK38DC19K9w9gLPT3WRBWJr8-s3SRncAag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Saturday, February 15, 2025, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
wrote:
> 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?
>
This is an inappropriate question for the -hackers mailing list. Both
-admin and -general are better places to get help on learning how to be a
DBA.
This list is basically for discussing potential patches to the codebase.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-02-16 01:15:15 | Re: BitmapHeapScan streaming read user and prelim refactoring |
| Previous Message | Rajesh Kumar | 2025-02-16 00:31:15 | Pg_stat_activity |