Re: What is impact of "varchar_opts"?

From: Edson Richter <edsonrichter(at)hotmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: What is impact of "varchar_opts"?
Date: 2013-01-21 22:16:14
Message-ID: BLU0-SMTP138A17A92AA8DD1E438D2C3CF170@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Em 21/01/2013 18:36, Tom Lane escreveu:
> Edson Richter <edsonrichter(at)hotmail(dot)com> writes:
>> Thanks, but I've found that some queries using LIKE operator uses table
>> scan instead index unless it is defined with varchar_ops in the index...
> You mean varchar_pattern_ops? That's an entirely different animal.
>
> regards, tom lane
>

Yeah, sure. The animal is me ;-) (just kidding, no offense!). I
expressed myself in wrong terminology, and wasted time. Sorry.

I mean varchar_pattern_ops. Most of my indexes with varchar fields need
to be created with this option to improve search with like operator.

Is there any way to specify this is the default option? What would be
the overall impact over the database?

Thanks,

Edson

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2013-01-21 22:38:24 Re: Case insensitive collation
Previous Message Kevin Grittner 2013-01-21 22:15:30 Re: Running update in chunks?