Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 6F0A79FB203 for ; Tue, 16 Jan 2007 06:13:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 57416-03 for ; Tue, 16 Jan 2007 06:13:30 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231]) by postgresql.org (Postfix) with ESMTP id D88709FB1F4 for ; Tue, 16 Jan 2007 06:13:30 -0400 (AST) Received: by wr-out-0506.google.com with SMTP id i20so112613wra for ; Tue, 16 Jan 2007 02:13:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=Te+LyC5DlTND0pApYqmcOrVF5xN79PYXuyZFCZwcF/4SEDhx060QA4HGwxcFjhRUO8lPMDE9miecuOuGDwYbwAPoiQqIvctoqL3tjl2tWAEslzMO4PfANn29uPCGKJokUrJI7XkYeIwmJikJSliofKaY0ypMpzLXGobb7J7BuCI= Received: by 10.65.240.5 with SMTP id s5mr821079qbr.1168942409550; Tue, 16 Jan 2007 02:13:29 -0800 (PST) Received: from ?192.168.0.39? ( [62.232.55.118]) by mx.google.com with ESMTP id p4sm7571189qba.2007.01.16.02.13.26; Tue, 16 Jan 2007 02:13:27 -0800 (PST) Message-ID: <45ACA53E.8080604@enterprisedb.com> Date: Tue, 16 Jan 2007 10:13:18 +0000 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.8 (X11/20061116) MIME-Version: 1.0 To: ramachandra.bhaskaram@wipro.com CC: pgsql-performance@postgresql.org Subject: Re: Caching in PostgreSQL References: <47230CE166B64744B0120173E4C2161E0103E70D@BLR-EC-MBX01.wipro.com> In-Reply-To: <47230CE166B64744B0120173E4C2161E0103E70D@BLR-EC-MBX01.wipro.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/239 X-Sequence-Number: 22840 ramachandra.bhaskaram@wipro.com wrote: > We were looking on how to improve the performance of our > application which is using PostgreSQL as backend. If postgreSQL is > supporting data page caching in the shared memory then we wanted to > design our application to read/write using the shared memory rather than > accessing the DB everytime so that, it will improve the performance of > our system. That's a bad idea. Just design your database schema with performance in mind, and use PostgreSQL normally with SQL queries. If you must, use a general-purpose caching library in your application, instead of trying to peek into PostgreSQL internals. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com