Hi there,
we got no comments on our proposal about changing GIN interface to
support multicolumn feature of GIN, see
http://archives.postgresql.org/message-id/[EMAIL PROTECTED]
for details, so here are some numbers demonstrating benefits and some
issues. Any help and feedback are welcome.
We
TODO/issues
- add support of other data types to btree_gin
done, now btree_gin supports int2, int4, int8, float4, float8, money, oid,
timestamp, timestamptz, time, timetz, date, interval, macaddr, inet, cidr, text,
varchar, char, bytea, bit and varbit types
--
Teodor Sigaev
We'd like to improve usefulness of a new multicolumn feature of GIN index (
already in CVS HEAD ), which is currently a bit limited because of lack of GIN
support for most data types. For example, it'd be very useful to combine native
GIN-supported data types, like text search, hstore, arrays w
