[Patch] Implement TODOs for index operator strategy number validation

From: Priyanka S <developerette(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: [Patch] Implement TODOs for index operator strategy number validation
Date: 2026-08-03 14:35:46
Message-ID: CA+Db6gb2-r2+PcuStf3Y7oviS9t7eTxDHisXLer4mtupqkXcqg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

This patch implements TODOs in the BRIN, GIN, GIST and SP-GIST index code.
Operator class validation is modified to add strategy number bounds
checking specific to each index type.
1) For BRIN and SP-GIST, the maximum strategy number from the common
RTStrategy list is used as the upper limit.
2) For SP-GIST, the number of GIS object types and the strategy numbers per
type are used to calculate the maximum strategy number.
3) As far as I can understand from the code, GIN may have custom
strategies, so the existing limit of 63 is retained.

I have tested this patch using 'make check' and 'make worldcheck'. All the
tests pass.

This is my first contribution, so any input would be appreciated.

Thanks & regards,
Priyanka

Attachment Content-Type Size
0001-Fix-TODOs-for-index-opclass-strategy-number-validati.patch text/x-patch 5.3 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-08-03 15:01:09 Re: Catcache rehash hits MaxAllocSize (1GB) and errors with "invalid memory alloc request size" on very large numbers of relations
Previous Message Ayush Tiwari 2026-08-03 14:24:32 Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments