Re: vacuum_cost_delay & VACUUM holding locks on GIST indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuum_cost_delay & VACUUM holding locks on GIST indexes
Date: 2005-03-01 00:59:15
Message-ID: 11357.1109638755@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-03-01 01:01:22 Re: invalid multibyte character for locale
Previous Message Tom Lane 2005-03-01 00:53:47 Re: Vacuum time degrading