Hackers,
after reading Heikki Linnakangas presentation about GIN from Nordic PGDay,
I figure out that btree_gin became much more attractive.
http://hlinnaka.iki.fi/presentations/NordicPGDay2014-GIN.pdf
But it have one weird behaviour: when you have range restriction like "col
> const1 AND col < c
On 03/28/2014 04:30 PM, Alexander Korotkov wrote:
> We have range types, and restriction "col <@ range" can be correctly
> handled by gin_extract_query, because it will be passed there as single
> restriction. This is workaround itself, but it's weird to force users
> express queries like this.
T
