Re: Query performance

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Joe Van Dyk <joe(at)tanga(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Query performance
Date: 2015-01-31 01:40:13
Message-ID: 54CC327D.6000202@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 1/25/15 2:03 AM, Pavel Stehule wrote:
> It might not always be an integer, just happens to be so here.
> Should I try text instead? I don't have to have the case-insensitive
> matching.
>
>
> text can be better

bytea would be even better yet, because that will always be a straight
binary comparison. text will worry about conversion and what not
(though, perhaps there's a way to force that to use C or SQL instead of
something like UTF8, short of changing the encoding of the whole database).
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim Nasby 2015-01-31 01:57:31 Re: Autocompletion with full text search
Previous Message Jim Nasby 2015-01-31 01:34:40 Re: working around JSONB's lack of stats?