Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Performance Issues


  • From: "Mark Woodward" <pgsql(at)mohawksoft(dot)com>
  • To: "Richard Huxton" <dev(at)archonet(dot)com>
  • Cc: "Dhanaraj M" <dhanaraj(dot)m(at)sun(dot)com>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Performance Issues
  • Date: Tue, 23 May 2006 13:04:10 -0400 (EDT)
  • Message-id: <17972(dot)24(dot)91(dot)171(dot)78(dot)1148403850(dot)squirrel(at)mail(dot)mohawksoft(dot)com>

> Dhanaraj M wrote:
>> I have the following doubts.
>>
>> 1. Does postgres create an index on every primary key?  Usually, queries
>> are performed against a table on the primary key, so, an index on it
>> will be very useful.
>
> Yes, a unique index is used to enforce the primary-key.

Well, here is an interesting question that I have suddenly become very
curious of, if you have a primary key, obviously a unique index, is it, in
fact, use this index regardless of analyzing the table?


>
>> 2. If 'm executing a complex query and it takes 10 seconds to return the
>> results -- it takes 10 seconds to execute the next time also.  I'm
>> wondering if there's any kind of caching that can be enabled -- so, the
>> next time it takes <10 seconds to return the results.
>
> Not of query results. Obviously data itself might be cached. You might
> want to look at memcached for this sort of thing.


I am looking at this string of posts and it occurs to me that he should
run analyze. Maybe I'm jumping at the wrong point.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group