I'd like to ask what do you mean in research item number 3?
3. Making the full-table sequential scan GIN-indexable instead seems very reasonable since GIN is primarily used to search for element values (PK values) that appear within composite items (FK array). a. Statistics have shown[7] that GIN indexing an array shows an increase in performance by ~2256% ! b. Thus the first step (as proposed ) would be to prove that “<@( is contained by)” can be used in this scope.
What exactly you're going to do in this item? Check that GIN index over array support given operator, do the performance benchmark or something else?
------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
