From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bill Studenmund <wrstuden(at)netbsd(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Subject: | Re: Proposed new create command, CREATE OPERATOR CLASS |
Date: | 2001-10-25 00:37:45 |
Message-ID: | 29926.1003970265@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bill Studenmund <wrstuden(at)netbsd(dot)org> writes:
> Do any of the access methods really support using non-binary operators?
Whether they do today is not the question. The issue is whether they
could --- and they certainly could.
> Oh gross. I just looked at contrib/intarray, and it defines two entries in
> pg_amop for amopstrategy number 20. They do happen to be commutators of
> each other. Look for the @@ and ~~ operators.
> 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?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-10-25 00:39:10 | Re: "Triggered data change violation", once again |
Previous Message | Bruce Momjian | 2001-10-25 00:34:52 | pgindent run |