GIN index is slow for update by its construction. When you update the rows with
or without columns indexed by GIN, postgres (in most cases) will insert new
records, so index insertion will occur. So, for large updates it's much cheaper
to drop and create index.
That was a one of reasons to develop fast_insert_gin patch which now in review
process.
Ivan Sergio Borgonovo wrote:
I've a table that contain a tsvector that is indexed (gin) and
triggers to update the tsvector that should then update the index.
--
Teodor Sigaev E-mail: teodor@xxxxxxxxx
WWW: http://www.sigaev.ru/
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
