Re: admin control over cancelling autovacuum when blocked by a lock - Mailing list pgsql-admin

From Rui DeSousa
Subject Re: admin control over cancelling autovacuum when blocked by a lock
Date
Msg-id ACF14079-4541-4300-978C-BEC42339B33F@crazybean.net
Whole thread Raw
In response to Re: admin control over cancelling autovacuum when blocked by a lock  (John Lumby <johnlumby@hotmail.com>)
Responses Re: admin control over cancelling autovacuum when blocked by a lock  (MichaelDBA <MichaelDBA@sqlexec.com>)
Re: admin control over cancelling autovacuum when blocked by a lock  (John Lumby <johnlumby@hotmail.com>)
List pgsql-admin


On Apr 30, 2019, at 9:27 AM, John Lumby <johnlumby@hotmail.com> wrote:

 it does do ANALYZE  -  in this context is that "DDL"?

I would consider that DDL and the application should avoid doing it; otherwise, you end up with blocking issues where both readers and writers are blocked unnecessarily.  The application issuing analyze on its own temp tables is fine and non blocking.  If you must analyze tables then I would limit which processes have access to those tables to avoid blocking issues.

I would look at your auto vacuum/analyze settings as oppose to the application issuing analyze commands as those are going to be a non blocking option.

pgsql-admin by date:

Previous
From: John Lumby
Date:
Subject: Re: admin control over cancelling autovacuum when blocked by a lock
Next
From: MichaelDBA
Date:
Subject: Re: admin control over cancelling autovacuum when blocked by a lock