Re: Index on two columns not used

From: Arnaud Lesauvage <thewild(at)freesurf(dot)fr>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Index on two columns not used
Date: 2006-10-18 14:15:13
Message-ID: 453636F1.7000903@freesurf.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Heikki Linnakangas a écrit :
> Arnaud Lesauvage wrote:
>> This query was taken from my "adminsitrative areas" model (continents,
>> countries, etc...). Whenever I query this model, I have to join many
>> tables.
>> I don't really know what the overhead of reading the heap-tuples is, but
>> would it be a good idea to add data-redundancy in my tables to avoid
>> joins ? (adding country_id, continent_id, etc... in the "cities" table)
>
> It depends. I would advise not to denormalize unless you really really
> have to. It's hard to say without more knowledge of the application.
>
> Is the query you showed a typical one? It ran in about 160 ms, is that
> good enough? It's doesn't sound too bad, considering that it returned
> almost 40000 rows.

It is quite typical, yes. It is the base query of a view. In
fact, most views have a lot more joins (they join with all
the upper-level tables).
But 150ms is OK, indeed.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Atesz 2006-10-18 14:24:30 ACCESS EXCLUSIVE lock
Previous Message Heikki Linnakangas 2006-10-18 13:57:25 Re: Index on two columns not used