btree index too small?

[pvgenuchten]

Description

We hit quite a lot that the btree index is defined too small on postgres to hold the content introduced by metadata elements, this typically occurs on the contacts and access constraints fields.

I wonder if the indexation code should limit the length of the field while inserting, based on the max allowed size of the btree index size

or is it more common to increase the size of the index?

Removing the index on that field would be another option, these fields are probably not used to filter, full text search is more relevant then

see also #398 and #942