Generalized Inverted Generalized Search Tree

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Generalized Inverted Generalized Search Tree
Date: 2010-05-14 04:03:45
Message-ID: 20100514130345.A452.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

We can index multiple scalar values per row with GIN access method,
and also can index single vector value per row with GiST AM.

Is it worth having a new AM to index multiple vector values per row?
It will be an AM for the missing feature in below:

| scalar | vector |
----------------+--------+--------+
single per row | btree | gist |
multi per row | gin | *HERE* |

We can call the new AM "gigist". Or, there might be another idea
to support expression indexes for SRF functions, like
=# CREATE TABLE tbl (c circle[]);
=# CREATE INDEX ON tbl USING gist (unnest(c));

Comments and ideas welcome.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-05-14 04:16:16 Re: nvarchar notation accepted?
Previous Message Tom Lane 2010-05-14 04:00:36 Re: nvarchar notation accepted?