Search Postgresql Archives

Re: vacuum_cost_delay & VACUUM holding locks on GIST indexes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ron Mayer <rm_pg@xxxxxxxxxxxxxxxxxxxxxxx> 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

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux