Skip site navigation (1)
Skip section navigation (2)
On 7/31/06, Manlio Perillo <manlio_perillo(at)libero(dot)it> wrote:
My guess is that the performance difference is not going to be noticable unless you are dealing with huge amounts of data and even then may account for such a small hit that there will be other issues that are more pressing like writing better queries, creating a data warehouse or adding proper indexes and keeping the indexes well maintained.
Anyone care to disagree?
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.com
==================================================================
Peripheral Links
Header And Logo
|
Site Navigation
Re: primary keys as TEXT
- From: "Aaron Bono" <postgresql(at)aranya(dot)com>
- To: "Manlio Perillo" <manlio_perillo(at)libero(dot)it>
- Cc: "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, pgsql-sql(at)postgresql(dot)org
- Subject: Re: primary keys as TEXT
- Date: Mon, 31 Jul 2006 14:34:49 -0500
On 7/31/06, Manlio Perillo <manlio_perillo(at)libero(dot)it> wrote:
Because serial ids are only surrogate keys.
My tables have well definited primary keys, the only problem is that
they are of type TEXT (and spawn up to 3 columns).
My concern is: how bad can be performance?
Anyone care to disagree?
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.com
==================================================================
- References:
- primary keys as TEXT
- From: Manlio Perillo
- Re: primary keys as TEXT
- From: Michael Glaesemann
- Re: primary keys as TEXT
- From: Manlio Perillo
- Re: primary keys as TEXT
- From: Aaron Bono
- Re: primary keys as TEXT
- From: Manlio Perillo
- primary keys as TEXT
- Prev by Date: Re: Triggers using PL/pgSQL
- Next by Date: Re: Joining a result set from four (4) tables
- Previous by thread: Re: primary keys as TEXT
- Next by thread: Re: primary keys as TEXT
- Indexes: