Re: vacuum_cost_delay & VACUUM holding locks on GIST indexes - Mailing list pgsql-general

From Tom Lane
Subject Re: vacuum_cost_delay & VACUUM holding locks on GIST indexes
Date
Msg-id 13436.1109651116@sss.pgh.pa.us
Whole thread Raw
In response to Re: vacuum_cost_delay & VACUUM holding locks on GIST  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
List pgsql-general
Ron Mayer <rm_pg@cheapcomplexdevices.com> writes:
> On Mon, 28 Feb 2005, Tom Lane wrote:
>> You could shorten the intervals for which the lock is held by reducing
>> vacuum_mem, but this might be counterproductive overall.

> Does this work?

[ thinks about it... ]  No, probably not; sorry for the misinformation.

Cutting vacuum_mem will reduce the number of index tuples that are to be
deleted during any one scan of the index.  But if the index is large,
it's probably the scanning time and not the deletion time that is dominant.

            regards, tom lane

pgsql-general by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Is any limitations in PostgreSQL?
Next
From: Sebastian Böck
Date:
Subject: Re: multicolumn GIST index question