> No, there's no support for indexes on varchar arrays (or any
> other kind
> of array). What sorts of things do you think such an index should be
> able to do?
Thanks for responding so quickly.
On a really high level, an index just associates the value to a
particular row, no? I would think an indexed array column would do the
same, except it would associate _each_ value from the array to that
particular row.
You might also want to only index a particular element, or a range of
elements from the array... instead of the entire thing.
Then you'd be able to do:
SELECT * FROM TABLE WHERE VARARR = 'Foo';
to get the all the rows that have 'Foo' somewhere in their VARARR column
w/o the need for the contrib/arrays package (which by the way is a very
useful package!).
I'm probably over simplifying.
Doing sequential scans (combined with the array iterator) against an
array column in a table with 8+ million records takes a little while...
What's the feasability of making this happen? I've seen your name
associated with a lot of the code. How difficult would it be for you to
implement? That would give me an indiciation of how difficult it would
be for me to implement. If you've thought about this, maybe you could
point me in the right direction?
thanks.
eric
