Thread: Antwort: Re: [SQLObject] Adding indexes to ID column?
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Waldemar la T. <wla...@ca...> - 2005-07-28 12:20:37
|
> Before trying to figure out what's going on, I'm going to ask "why?" > > The ID column is set as the primary key for the table. Any sane > database maintains an index for the primary key automatically, so no > other indexing is required for doing primary key searches. > > Kevin The database access seemed to me simply to slow. So I added some useful indexes and because we use the id column in some of our views pretty extensively, my guess was we have to index the ID column, too. I did not know that it is automatically indexed. Is this true for PostgreSQL, too? I will run some simple tests. The access simply seems to slow with some 10000s of rows. OK, thanks anyway. Waldemar la Tendresse |
From: Kevin D. <da...@gm...> - 2005-07-27 12:53:33
|
On 7/27/05, Waldemar la Tendresse <wla...@ca...> wrote: > The database access seemed to me simply to slow. So I added some useful > indexes and because we use the id column in some > of our views pretty extensively, my guess was we have to index the ID > column, too. I did not know that it is automatically indexed. Is this > true for PostgreSQL, too? I will run some simple tests. The access simply > seems to slow with some 10000s of rows. It's certainly worth checking, but I would be amazed if the problem was that PostgreSQL is not using an index for the primary key. This page: http://www.postgresql.org/docs/7/interactive/indices.htm says that the SQL standard doesn't specify that the primary key is efficiently accessed. However, in practice, database vendors know that the primary key is used for common lookups and joins, so they would undoubtedly use an efficient structure. Kevin |