pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vernon Wu <vernonw@gatewaytech.com>
To: mlennert@club.worldonline.be, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: performance question
Date: Mon, 20 Jan 2003 21:32:25 -0800
Message-ID: <ED1UMKFDE0A6MIJF1ZDC8563A8OK3Y87.3e2cdb69@kimiko> (raw)
In-Reply-To: <20147.1043095100@sss.pgh.pa.us>

20/01/2003 12:38:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>"Moritz Lennert" <mlennert@club.worldonline.be> writes:
>> One question I asked myself is whether the use of char(2) is the best
>> option.
>
>It may not be, particularly if you are running in a non-English locale.
>Comparisons will invoke the standard library routine strcoll(), which is
>depressingly slow in some locales, at least on some platforms.
>


In the case of selection operations involving multiple tables joined by userid that can be in various languages, is a 
potential performance trouble spot? Considering the number of tables anywhere from ten to twenty.



>> The column (and most others in the table) contains codes that
>> designate different characteristics (for ex. in a column 'sex' one would
>> find '1'=male, '2'=female).
>
>If you are using numeric codes you are surely better off storing them
>as integer or perhaps smallint (integer is less likely to create type
>mismatch headaches, though).  In the above example you are getting the
>worst of both worlds: there's no mnemonic value in your data entries,
>*and* you're paying for textual comparisons.
>
>			regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>






view thread (19+ messages)  latest in thread

Message-ID: <ED1UMKFDE0A6MIJF1ZDC8563A8OK3Y87.3e2cdb69@kimiko>
Permalink:  ../ED1UMKFDE0A6MIJF1ZDC8563A8OK3Y87.3e2cdb69@kimiko/
Also on:    postgresql.org/message-id/ED1UMKFDE0A6MIJF1ZDC8563A8OK3Y87.3e2cdb69@kimiko

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: vernonw@gatewaytech.com, tgl@sss.pgh.pa.us
  Subject: Re: performance question
  In-Reply-To: <ED1UMKFDE0A6MIJF1ZDC8563A8OK3Y87.3e2cdb69@kimiko>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox