Embedded zeroes aren't supported in
> char/varchar/text fields,
> and cannot be supported in a portable fashion, since
> these datatypes
> rely on functions like strcoll() that don't allow
> embedded nulls in
> strings. It wouldn't surprise me too much if there
> are inconsistent
> behaviors between indexscans and seqscans for such
> invalid data.
>
> It doesn't seem real practical for us to examine the
> output of every
> C-coded function to make sure it produces a valid
> value of the datatype.
> Illegal returned values are a fault of the function,
> and ensuing
> misbehaviors are still its fault ...
Fair enough, but I think it should raise a caution
flag when two different behaviors can be seen with the
same query. This may have a common cause with other
index vs non-index behavior.
__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
