Re: GIN: Implementing triConsistent and strategy number

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN: Implementing triConsistent and strategy number
Date: 2015-06-26 14:13:42
Message-ID: 558D5E16.2060109@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/24/2015 11:11 PM, Jeff Janes wrote:
> Is there a way to implement triConsistent for only some of the strategy
> numbers?

No.

> It looks like I would have to internally re-implement something like
> shimTriConsistentFn for each strategy number for which I don't want to
> implement the ternary system in full. Am I missing a trick?

Hmm. It didn't occur to me that you might want to implement
tri-consistent for some strategy numbers and fall back to the
shim-implementation for others. Do you have a real-world example of
where that'd be useful?

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-06-26 14:21:59 Re: Nitpicking: unnecessary NULL-pointer check in pg_upgrade's controldata.c
Previous Message Andres Freund 2015-06-26 13:59:38 Re: Should we back-patch SSL renegotiation fixes?