Message-ID: <4CF53B0B.8060906@gmail.com>
Date: Tue, 30 Nov 2010 10:57:31 -0700
From: Rob Sargent <robjsargent@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.15) Gecko/20101026 SUSE/3.0.10 Lightning/1.0b1
	Thunderbird/3.0.10
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
References: <4CF53797.4040806@gmail.com>
	<AANLkTikG8WZobuN=i3GbRPjPH8FYZC9YC5oUdrOpUfUt@mail.gmail.com>
In-Reply-To: <AANLkTikG8WZobuN=i3GbRPjPH8FYZC9YC5oUdrOpUfUt@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: indexing longish string

If the performance against an index doesn't cut it, we would be forced
to choose just such an implementation, but if pg can do it straight up
that would be less work for us.  A good thing, to be sure.

On 11/30/2010 10:50 AM, jose wrote:
> Why don't you use some type of hash like md5 for indexing ?
> 
> 2010/11/30 Rob Sargent <robjsargent@gmail.com>:
>> Were we to create a table which included a text field for a small block
>> of xml (100-1000 chars worth), would an index on that field be useful
>> against exact match queries?
>>
>> We're wondering if a criterion such as "where 'a string expected to be
>> of size range 100 to 500' = tabelWithStrings.stringSearched" would make
>> good use of an index on "stringSearched" column.
>>
>> The key is that there will only be exact match queries.
>>
>> Thanks for your thoughts.
>>
>>
>>
>> --
>> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-sql
>>
>