| From: | rihad <rihad(at)mail(dot)ru> |
|---|---|
| To: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | 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:35:20 |
| Message-ID: | 8472c827-210b-7262-dcef-9c730b14a24c@mail.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/01/2019 08:30 PM, Michel Pelletier wrote:
>
>
> On Sun, Mar 31, 2019 at 10:49 PM David Rowley
> <david(dot)rowley(at)2ndquadrant(dot)com <mailto: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.
It is actually refreshed concurrently.
>
>
> --
> David Rowley http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glenn Schultz | 2019-04-01 17:37:00 | Help with insert query |
| Previous Message | Michel Pelletier | 2019-04-01 16:30:18 | Re: Gigantic load average spikes |