Re: text_pattern_ops index *not* used in field = value condition?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: text_pattern_ops index *not* used in field = value condition?
Date: 2007-09-15 16:21:34
Message-ID: 20070915162134.GA19061@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Sep 15, 2007 at 11:48:19AM -0400, Tom Lane wrote:
> As of a couple years ago, the regular text = operator only yields true
> for bitwise-equal strings, so we could perhaps drop ~=~ and use = in its
> place. But I'd be worried about breaking existing queries that expect
> the strangely-named operator to be there.

ok. fair enough. it's clearer now.

best regards,

depesz

--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly paid DBA. here's my CV!" :)
http://www.depesz.com/ - blog dla ciebie (i moje CV)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2007-09-15 17:32:43 Re: getting min/max of two values
Previous Message Tom Lane 2007-09-15 15:48:19 Re: text_pattern_ops index *not* used in field = value condition?