Re: Lock problem with autovacuum truncating heap

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lock problem with autovacuum truncating heap
Date: 2011-03-27 19:25:05
Message-ID: 4D8F8F11.6060309@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/27/2011 1:24 PM, Simon Riggs wrote:
> So we should truncate in 16MB chunks also.

On a second though, fiddling with the scan direction is probably too
much of a change for back releases anyway. That 8.3/8.4 can get into a
situation, where autovacuum causes a 12 minute freeze of a production
server could be argued as a bug. Likewise that 9.0 will never succeed to
truncate but cause a 1 second hiccup every two minutes.

Since we are talking about stable releases, I think just releasing and
reacquiring the exclusive lock is enough. We can then try to further
improve things for future releases.

Jan

--
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-03-27 19:40:22 Re: SSI bug?
Previous Message Greg Smith 2011-03-27 19:20:12 Re: Performance Farm Release