From: | m w <mttf2000(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Like vs '=' bug with indexing |
Date: | 2001-02-03 22:44:30 |
Message-ID: | 20010203224430.61330.qmail@web12405.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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/
From | Date | Subject | |
---|---|---|---|
Next Message | Rick Robino | 2001-02-04 04:44:47 | Re: configure.in patch for readline and curses. |
Previous Message | Tom Lane | 2001-02-03 22:27:49 | Re: Like vs '=' bug with indexing |