| From: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | rihad <rihad(at)mail(dot)ru>, hjp-pgsql(at)hjp(dot)at, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Gigantic load average spikes |
| Date: | 2019-04-01 16:30:18 |
| Message-ID: | CACxu=vKyhWUDsh-xdtaJTr66SaQ7chfyuDFW0RDxyZMEPuMDUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Mar 31, 2019 at 10:49 PM David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:
>
> Perhaps a bunch of processes waiting on the access exclusive lock on
> the materialized view being released?
>
> log_lock_waits might help you if the MV takes more than a second to
> refresh, otherwise, you might need to have a look at ungranted locks
> in pg_locks and see if the number of locks spikes during the refresh.
>
I think David's got the right idea here. Like he said, investigate
pg_locks, if it is the refresh materialized view, you can avoid the problem
by doing 'REFRESH MATERIALIZED VIEW CONCURRENTLY'. You will need at least
one unique index on the table.
> --
> David Rowley http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rihad | 2019-04-01 16:35:20 | Re: Gigantic load average spikes |
| Previous Message | Foo Bar | 2019-04-01 16:24:02 | Re: WAL Archive Cleanup? |