Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
28.0.0
-
-
CP: sprint 77, CP: sprint 78, CP: sprint 79
-
3
-
Core: Platform
Description
PostgreSQL returns an error like "index row size 3256 exceeds maximum 2712 for index" if a string to be indexed by an b-tree exceeds the maximum index row size. RMB should truncate the string using left(string, 600) when using a b-tree. A UTF-8 character can be up to 4 bytes long, 4*600 < 2712.
This still allows to use the index for sorting and for matching (exact and right truncation).
Note for exact and right truncation matching: If the search string is up to 600 characters long use left(field, 600) = searchstring. If the search string is longer than 600 characters use left(field, 600) = left(searchstring, 600) AND field = searchstring to make use of the index and afterwards filter using the complete field.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODINVSTOR-139 Indices for sorting: Only index first part of JSON array properties
-
- Closed
-
-
MODINVSTOR-379 Reindex of contributors fails with maximum 2712 'index row size exceeded' error
-
- Closed
-
-
MODINVSTOR-390 Adding an Instance with a longer title throws "Values larger than 1/3 of a buffer page cannot be indexed"
-
- Closed
-
-
MODINVSTOR-395 Adding a Instance record with a few more contributors than normal throws "Values larger than 1/3 of a buffer page cannot be indexed" exception
-
- Closed
-
- is blocked by
-
RMB-533 Performance: Fix lower/f_unaccent usage by checking all 5 index types
-
- Closed
-
- relates to
-
MODINVSTOR-430 RMB 29.2.2.: Upgrade indexes on module upgrade
-
- Closed
-
-
MODUSERS-168 RMB 29.2.2: Upgrade indexes on module upgrade
-
- Closed
-
-
FOLIO-2402 platform-related features and fixes for mod-inv-stor 18.2.1
-
- Closed
-
-
RMB-550 Index recreation on module upgrade
-
- Closed
-
-
RMB-646 order with distinct on fails for sort.descending
-
- Closed
-