Re: BUG #13472: VACUUM ANALYZE hangs on certain tables

From: Andres Freund <andres(at)anarazel(dot)de>
To: Matthew Seaman <matthew(dot)seaman(at)adestra(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13472: VACUUM ANALYZE hangs on certain tables
Date: 2015-06-26 15:58:45
Message-ID: 20150626155845.GA30708@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2015-06-26 16:21:19 +0100, Matthew Seaman wrote:
> Restarting the DB is going to require all sorts of outage notifications
> and general palaver, so we'd definitely prefer not to that if we can
> possibly avoid it.

Is it feasible to lock the table exclusively for a short time? If so you
can just VACUUM FULL them - given the table sizes that should be fairly
quick.

(The difference between table level exclusive locks and cleanup locks is
that the latter aren't "fair", i.e. a continious stream of pins will
block them, whereas heavyweight locks are queued)

- Andres

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2015-06-26 16:34:46 Re: BUG #13470: Logical replication 'invalid memory alloc'
Previous Message Matthew Seaman 2015-06-26 15:39:10 Re: BUG #13472: VACUUM ANALYZE hangs on certain tables