On Tue, Sep 8, 2015 at 4:21 PM, Tomas Vondra
wrote:
> On 09/08/2015 09:15 PM, Merlin Moncure wrote:
> ...
>>>
>>> I just had the exact same problem, and indeed gin fares much better.
>>
>>
>> Also, with 9.5 we will see much better worst case performance from gin
>> via Jeff's patch:
>>
>> http://g
On 09/08/2015 09:15 PM, Merlin Moncure wrote:
...
I just had the exact same problem, and indeed gin fares much better.
Also, with 9.5 we will see much better worst case performance from gin
via Jeff's patch:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=97f3014647a5bd57003
On Thu, Sep 3, 2015 at 6:19 PM, Claudio Freire wrote:
> On Wed, Sep 2, 2015 at 4:29 PM, Jeff Janes wrote:
>> On Wed, Sep 2, 2015 at 7:00 AM, Volker Böhm wrote:
>>>
>>>
>>>
>>> CREATE INDEX trgm_adresse ON adressen.adresse USING gist
>>> (normalize_string((btrimnormalize_stringCOALESC
On Wed, Sep 2, 2015 at 4:29 PM, Jeff Janes wrote:
> On Wed, Sep 2, 2015 at 7:00 AM, Volker Böhm wrote:
>>
>>
>>
>> CREATE INDEX trgm_adresse ON adressen.adresse USING gist
>> (normalize_string((btrimnormalize_stringCOALESCE((vorname)::text,
>> ''::text) || ' '::text) || (name1)::tex
On Wed, Sep 2, 2015 at 7:00 AM, Volker Böhm wrote:
>
>
> CREATE INDEX trgm_adresse ON adressen.adresse USING gist
> (normalize_string((btrimnormalize_stringCOALESCE((vorname)::text,
> ''::text) || ' '::text) || (name1)::text))::character varying,
> (-1)))::text || ' '::text) || (nor
Hi,
I have a table for addresses:
CREATE TABLE adressen.adresse
(
pool_pk integer NOT NULL,
adressnr_pk integer NOT NULL,
anrede varchar(8),
vorname varchar(50) DEFAULT ''::character varying NOT NULL,
name1varchar(100)NOT NULL,
na