Ron Mayer <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
