| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Marti Raudsepp <marti(at)juffo(dot)org> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: btree_gin and ranges |
| Date: | 2014-10-22 12:01:15 |
| Message-ID: | 54479C8B.3080809@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Shouldn't this be implemented in a more generic manner? An ordinary
Unfortunately I don't see a way for that. GIN is generalized - and it doesn't
know semantic. Actually, we could fix first five strategy numbers for BTree's
strategies, and then we could teach GIN core to use BTRee semantic, but what
about with already existed operator classes?
>
> The documentation describes btree-gin as providing "GIN operator
> classes that implement B-tree equivalent behavior", but now the
> behavior diverges.
Anyway GIN couldn't be used for ORDER BY clause.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-10-22 12:27:29 | Re: [Windows,PATCH] Use faster, higher precision timer API |
| Previous Message | Heikki Linnakangas | 2014-10-22 11:53:53 | Re: BUG: *FF WALs under 9.2 (WAS: .ready files appearing on slaves) |