From: Tom Lane <tgl@sss.pgh.pa.us>
To: Emre Hasegeli <emre@hasegeli.com>
Cc: Pujol Mathieu <mathieu.pujol@realfusio.com>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: GIST optimization to limit calls to operator on sub nodes
Date: Sun, 29 Jun 2014 16:30:22 -0400
Message-ID: <4113.1404073822@sss.pgh.pa.us> (raw)
In-Reply-To: <20140629201419.GA63570@hasegeli.local>
References: <53A7D547.5080302@realfusio.com>
<20140629201419.GA63570@hasegeli.local>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Emre Hasegeli <emre@hasegeli.com> writes:
> Pujol Mathieu <mathieu.pujol@realfusio.com>:
>> I made my own index to handle specific data and operators. It works
>> pretty fine but I wonder if it was possible to optimize it.
>> When I run my operator on a GIST node (in the method
>> gist_range_consistent) it returns "NotConsistent" /
>> "MaybeConsistent" / "FullyConsistent".
>> NotConsistent -> means that all subnodes could be ignored,
>> gist_range_consistent return false
>> MaybeConsistent -> means that at least one subnode/leaf will be
>> consistent, gist_range_consistent return true
>> FullyConsistent -> means that all subnodes/leaves will be
>> consistent, gist_range_consistent return true
>>
>> So like with the "recheck flag" I would like to know if there is a
>> way to notify postgres that it is not necessary to rerun my operator
>> on subnodes, to speedup the search.
> I do not think it is possible at the moment. The GiST framework can
> be extended to support this use case. I am not sure about the
> speedup. Most of the consistent functions do not seem very expensive
> compared to other operations of the GiST framework. I would be
> happy to test it, if you would implement.
I don't actually understand what's being requested here that the
NotConsistent case doesn't already cover.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, emre@hasegeli.com, mathieu.pujol@realfusio.com
Subject: Re: GIST optimization to limit calls to operator on sub nodes
In-Reply-To: <4113.1404073822@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox