| From: | kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Raj <rajeshkumar(dot)dba09(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Slowness |
| Date: | 2026-04-17 07:19:25 |
| Message-ID: | CA+427g_WWkt-QcqbOOruG3WEwpkOrhPER51Dp29wd7MoFnVchw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
If "customer says they are facing slowness" then my three first steps
usually are
1) grep "ERROR:\|FATAL:" server.log
2) top. Maybe there is some unexpected process(es). Use a f, to sort by
mem, cpu etc
3) query:
select datname, usename, client_addr, leader_pid, pid, DATE_TRUNC('second',
query_start) query_start, wait_event_type, wait_event, query_id from
pg_stat_activity where xact_start is not NULL order by 6;
and
\watch
And take a look at wait_event_type, wait_event
It gives glance, what is currently going on.
br
Kaido
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pär Mattsson | 2026-04-29 09:28:35 | User Mapping? |
| Previous Message | Eduar Flow | 2026-04-15 23:42:30 | Re: Update postgresql via offline mode |