Re: Proposal: fix range queries in btree_gin

From: Antonin Houska <antonin(dot)houska(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: fix range queries in btree_gin
Date: 2014-03-28 16:19:57
Message-ID: 5335A12D.50701@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Honza 2014-03-28 16:22:14 Store data in pg_toast for custom type fails (bug?)
Previous Message Tom Lane 2014-03-28 15:50:56 Re: UNION ALL on partitioned tables won't use indices.