Re: Performance Issues - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: Performance Issues
Date
Msg-id 77B03FE1-0B4E-47D7-8B4D-0CFB2DDC7783@fastcrypt.com
Whole thread Raw
In response to Re: Performance Issues  (Richard Huxton <dev@archonet.com>)
List pgsql-hackers
On 23-May-06, at 10:24 AM, Richard Huxton wrote:

> 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.

Postgresql relies on the kernel buffers, and shared buffers for caching.

As someone else said postgresql is quite conservative when shipped.  
Tuning helps considerably

Dave
>
> -- 
>   Richard Huxton
>   Archonet Ltd
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>



pgsql-hackers by date:

Previous
From: Csaba Nagy
Date:
Subject: Re: error-free disabling of individual child partition
Next
From: Simon Riggs
Date:
Subject: Re: [ADMIN] does wal archiving block the current client