| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Joe Van Dyk <joe(at)tanga(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Query performance |
| Date: | 2015-01-31 06:28:08 |
| Message-ID: | CAFj8pRD==gcFXqYE+vX-e+CAqrN9Zs88rda5z28xG1PNEzqxNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2015-01-31 2:40 GMT+01:00 Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>:
> 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).
>
true,
good idea
Regards
Pavel
> --
> Jim Nasby, Data Architect, Blue Treble Consulting
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Weyer | 2015-01-31 16:00:42 | Unexpected (bad) performance when querying indexed JSONB column |
| Previous Message | Jim Nasby | 2015-01-31 02:01:16 | Re: Performance of Postgresql Foreign Data Wrapper |