| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | PegoraroF10 <marcos(at)f10(dot)com(dot)br>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Too slow to create new schema and their tables, functions, triggers. |
| Date: | 2019-07-26 14:28:36 |
| Message-ID: | 5d1d5304-d64f-8079-1e7e-167f7cf0e662@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 7/26/19 4:15 AM, PegoraroF10 wrote:
> select count(*), count(*) filter (where last_autovacuum is not null) from
> pg_stat_all_tables
> count count
> 36605 1178
>
> But what tables should I see if vacuum ran on it ?
I would recommend reading this:
https://www.postgresql.org/docs/11/routine-vacuuming.html
and in particular:
https://www.postgresql.org/docs/11/routine-vacuuming.html#AUTOVACUUM
For now look at the actual values of last_autovacuum to see how current
the autovacuuming is. My guess is that the issues you are having has to
do with bloat in the system tables, so I would start there.
>
>
>
> --
> Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2019-07-26 16:45:40 | Re: Too slow to create new schema and their tables, functions, triggers. |
| Previous Message | Adrian Ho | 2019-07-26 14:13:50 | Re: Running concurrent txns and measuring the timings in Postgres |