From: | "David Levy" <dvid(dot)levy(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | ramachandra(dot)bhaskaram(at)wipro(dot)com, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Caching in PostgreSQL |
Date: | 2007-01-16 10:29:14 |
Message-ID: | 52543fce0701160229v35c7fa5fvc2da2d3aebf5a7e0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I am using memcached (http://www.danga.com/memcached/) to cache Postgres
ADODB recordsets.
It's very efficient but has to be implemented in your own application.
On 1/16/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
>
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
David LEVY aka Selenium
Zlio.com & Col.fr
Blog : http://www.davidlevy.org
ZlioShop : http://shop.davidlevy.org
From | Date | Subject | |
---|---|---|---|
Next Message | Gauri Kanekar | 2007-01-16 13:48:17 | Table Size |
Previous Message | Heikki Linnakangas | 2007-01-16 10:13:18 | Re: Caching in PostgreSQL |