Re: Proposed new create command, CREATE OPERATOR CLASS - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: Proposed new create command, CREATE OPERATOR CLASS
Date
Msg-id 3BD7D2F2.1040300@stack.net
Whole thread Raw
In response to Re: Proposed new create command, CREATE OPERATOR CLASS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposed new create command, CREATE OPERATOR CLASS
Re: Proposed new create command, CREATE OPERATOR CLASS
List pgsql-hackers
>>Wait a second, how can you do that? Doesn't that violate
>>pg_amop_opc_strategy_index ?
>>
> 
> It sure does, but running the script shows that the second insert
> doesn't try to insert any rows.  There's no entry in the temp table
> for ~~ because its left and right operands are not the types the
> SELECT/INTO is looking for.
> 
> This is evidently a bug in the script.  Oleg?
> 


Make me right if I mistake.

When we was developing operator @@, I saw that postgres don't use index in 
select if operation has not commutator. But operator with different types in 
argument can't be commutator with itself. So I maked operator ~~ only for 
postgres can use index access for operator @@. There is no any difficulties to 
adding index support for operator ~~. The same things is with contrib/tsearch 
module.

But I think that there is not any other necessity in presence ~~.



-- 
Teodor Sigaev
teodor@stack.net




pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: timeout for "idle in transaction"
Next
From: Lincoln Yeoh
Date:
Subject: Re: storing binary data