Postgres Pro
Downloads
Home   >   mailing lists

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 11357.1109638755@sss.pgh.pa.us
Whole thread Raw
In response to vacuum_cost_delay & VACUUM holding locks on GIST indexes  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
Responses Re: vacuum_cost_delay & VACUUM holding locks on GIST  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
List pgsql-general
Tree view 
Ron Mayer <rm_pg@cheapcomplexdevices.com> writes:
> When you VACUUM a table with postgis indexes (perhaps GIST indexes
> in general?) it seems a lock is held on the table.

GIST isn't concurrent-safe.

> Any clever workarounds?

Fix GIST ;-)

You could shorten the intervals for which the lock is held by reducing
vacuum_mem, but this might be counterproductive overall.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Vacuum time degrading
Next
From: Tom Lane
Date:
Subject: Re: invalid multibyte character for locale