This is a discussion on Re: Caching in PostgreSQL within the Pgsql Performance forums, part of the PostgreSQL category; --> Hi Heikki Linnakangas, Thanks for yoru kind response. We were looking on how to improve the performance of our ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi Heikki Linnakangas, Thanks for yoru kind response. 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. If this is possible can you please tell us how can we implement the same. Any idea on the same is of very much help. Thanks in Advance, Ramachandra B.S. -----Original Message----- From: Heikki Linnakangas [mailto:hlinnaka@gmail.com] On Behalf Of Heikki Linnakangas Sent: Tuesday, January 16, 2007 3:04 PM To: Ramachandra Bhaskaram (WT01 - IP-Multimedia Carrier & Ent Networks) Cc: pgsql-performance@postgresql.org Subject: Re: [PERFORM] Caching in PostgreSQL ramachandra.bhaskaram@wipro.com wrote: > > Hi, > > Can anybody tell me how can I implement data Caching in the shared > memory using PostgreSQL. PostgreSQL, like most other DBMS, caches data pages in shared memory. What exactly are you trying to accomplish? Are you having a performance problem? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
| |||
| 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 ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| 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@enterprisedb.com> wrote: > > 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 > > ---------------------------(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 |