Re: querying both text and non-text properties - Mailing list pgsql-general

From Rob Nikander
Subject Re: querying both text and non-text properties
Date
Msg-id 98C9D9E1-D404-47E2-A04A-B41EC2A025E3@gmail.com
Whole thread Raw
In response to Re: querying both text and non-text properties  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: querying both text and non-text properties  (Tony Shelver <tshelver@gmail.com>)
List pgsql-general

> On Dec 4, 2018, at 4:59 PM, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> You have two options:
>
> A combined index:
>
>  CREATE EXTENSION btree_gin;
>  CREATE INDEX ON fulltext USING gin (to_tsvector('english', doc), color);
>
> That is the perfect match for a query with
>
>  WHERE color = 'red' AND to_tsvector('german', doc) @@ to_tsquery('english', 'word');
>
> But you can also create two indexes:
>
>  CREATE INDEX ON fulltext USING gin (to_tsvector('english', doc));
>  CREATE INDEX ON fulltext (color);
>
> Then you don't need the extension, and PostgreSQL can still use them for the search,
> either only one of them if the condition is selective enough, or a "BitmapAnd" of both.

Thanks! I will try both these methods and compare the performance.

Rob

pgsql-general by date:

Previous
From: Raymond Brinzer
Date:
Subject: Re: simple division
Next
From: Dejan Petrovic
Date:
Subject: Database corruption in cascaded replica, "pg_xact/003A" doesn'texist, reading as zeroes"