From: Heikki Linnakangas <heikki@enterprisedb.com>
To: ramachandra.bhaskaram@wipro.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching in PostgreSQL
Date: Tue, 16 Jan 2007 10:13:18 +0000
Message-ID: <45ACA53E.8080604@enterprisedb.com> (raw)
In-Reply-To: <47230CE166B64744B0120173E4C2161E0103E70D@BLR-EC-MBX01.wipro.com>
References: <47230CE166B64744B0120173E4C2161E0103E70D@BLR-EC-MBX01.wipro.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: heikki@enterprisedb.com, ramachandra.bhaskaram@wipro.com
Subject: Re: Caching in PostgreSQL
In-Reply-To: <45ACA53E.8080604@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox