Re: Vacuum, Freeze and Analyze: the big picture - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Vacuum, Freeze and Analyze: the big picture
Date
Msg-id 51ACE6E3.4000309@agliodbs.com
Whole thread Raw
In response to Vacuum, Freeze and Analyze: the big picture  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Vacuum, Freeze and Analyze: the big picture  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 06/03/2013 11:12 AM, Andres Freund wrote:
> On 2013-06-03 11:00:38 -0700, Josh Berkus wrote:
>>
>>>> Also, locking while it does its work.
>>>
>>> Eh?
>>
>> Even if we're doing lazy vacuum, we have to lock a few pages at a time
>> of each table.  This does result in response time delays on the current
>> workload, which can be quite bad if it's a highly contended table already.
> 
> We don't really lock more pages at a time than normal DML does. 1 heap
> page at a time, possibly several index pages at once.

Really?  I though vacuum held onto its locks until it reached
vacuum_cost.  If it doesn't, then maybe we should adjust the default for
vacuum_cost_limit upwards.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: UTF-8 encoding problem w/ libpq
Next
From: Robert Haas
Date:
Subject: Re: MVCC catalog access