From: | "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Implied Functional Index use |
Date: | 2006-07-13 07:14:47 |
Message-ID: | E1539E0ED7043848906A8FF995BDA579012B3E36@m0143.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > - add a new boolean to pg_operator to allow us to define which
> > > operators offer true equality ...
> >
> > This would be useful for other purposes too, as we keep coming up
> > against "what's the equality operator for this datatype" problems.
> > However, the restriction to "true" equality, such that we can assume
x
> > = y implies f(x) = f(y) for every immutable function f on the
datatype
Maybe we could have a tri (or more) state flag for the equality
operators.
' ' .. not an equality op
'e' .. equality
's' .. strict equality (op only true iff the binary representation is
equal)
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-07-13 07:16:03 | Re: pre_load_libraries |
Previous Message | Joshua D. Drake | 2006-07-13 05:35:11 | Re: Three weeks left until feature freeze |