Re: Proposal: fix range queries in btree_gin - Mailing list pgsql-hackers

From Antonin Houska
Subject Re: Proposal: fix range queries in btree_gin
Date
Msg-id 5335A12D.50701@gmail.com
Whole thread Raw
In response to Proposal: fix range queries in btree_gin  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
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.

This reminds me of my earlier experiment

http://www.postgresql.org/message-id/51FBC99D.7040506@gmail.com

even though my motivation was different: to make comparePartial()
support function unnecessary.

// Antonin Houska (Tony)




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: UNION ALL on partitioned tables won't use indices.
Next
From: Honza
Date:
Subject: Store data in pg_toast for custom type fails (bug?)