| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Dhanaraj M <Dhanaraj(dot)M(at)Sun(dot)COM> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Performance Issues |
| Date: | 2006-05-23 14:24:01 |
| Message-ID: | 44731B01.6070003@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
> 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.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-05-23 14:24:17 | Re: error-free disabling of individual child partition |
| Previous Message | Tom Lane | 2006-05-23 14:19:09 | Re: error-free disabling of individual child partition |