Skip site navigation (1) Skip section navigation (2)

Re: BUG #5946: Long exclusive lock taken by vacuum (not full)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Maxim Boguk" <Maxim(dot)Boguk(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Date: 2011-03-25 15:17:19
Message-ID: 4345.1301066239@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Maxim Boguk" <Maxim(dot)Boguk(at)gmail(dot)com> writes:
> In my case vacuum tried to truncate last 10-15GB from 100Gb relation, and
> each time (3) it was cost 10+ minutes of service downtime (because that
> table was completely locked).

> Is  that correct behaviour? Are here any way to speedup that process or at
> least allow read-only queries during that time?

Use autovacuum --- if there's something that wants to access the table,
autovac will get kicked off the lock.  (Of course, the table may never
get truncated then, but maybe you don't care.)

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Jim WoodworthDate: 2011-03-25 15:27:31
Subject: checking on bug #5917
Previous:From: Kris JurkaDate: 2011-03-25 15:00:31
Subject: Re: BUG #5948: JDBC wrond insert of timestamp data

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group