From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | ramachandra(dot)bhaskaram(at)wipro(dot)com |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Caching in PostgreSQL |
Date: | 2007-01-16 10:13:18 |
Message-ID: | 45ACA53E.8080604@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
ramachandra(dot)bhaskaram(at)wipro(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David Levy | 2007-01-16 10:29:14 | Re: Caching in PostgreSQL |
Previous Message | ramachandra.bhaskaram | 2007-01-16 09:43:09 | Re: Caching in PostgreSQL |