pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedCaching in PostgreSQL
6+ messages / 4 participants
[nested] [flat]
* Caching in PostgreSQL
@ 2007-01-16 08:43 ramachandra.bhaskaram@wipro.com
0 siblings, 2 replies; 6+ messages in thread
From: ramachandra.bhaskaram@wipro.com @ 2007-01-16 08:43 UTC (permalink / raw)
To: pgsql-performance
Hi,
Can anybody tell me how can I implement data Caching in the
shared memory using PostgreSQL.
For one of the projects we are using Postgres version 8.0.3 and
were planning to support table partitioning in order to improve the DB
query/update performance but, it will be very much helpful if anybody
can tell me whether data cache is possible in Postgres.
We also, need to know if the DB view is kept in the DB Managers program
memory or in the shared memory of the processor. If it is in the shared
memory, we only need to know the shared memory address/name so that we
can access. If not in shared memory then we need know whether it is
possible to make the postgress to store the DB view in shared memory.
Thanks in Advance,
Ram.
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Caching in PostgreSQL
@ 2007-01-16 09:33 Heikki Linnakangas <heikki@enterprisedb.com>
parent: ramachandra.bhaskaram@wipro.com
1 sibling, 0 replies; 6+ messages in thread
From: Heikki Linnakangas @ 2007-01-16 09:33 UTC (permalink / raw)
To: ramachandra.bhaskaram@wipro.com; +Cc: pgsql-performance
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Caching in PostgreSQL
@ 2007-01-16 09:43 ramachandra.bhaskaram@wipro.com
0 siblings, 1 reply; 6+ messages in thread
From: ramachandra.bhaskaram@wipro.com @ 2007-01-16 09:43 UTC (permalink / raw)
To: heikki@enterprisedb.com; +Cc: pgsql-performance
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Caching in PostgreSQL
@ 2007-01-16 10:13 Heikki Linnakangas <heikki@enterprisedb.com>
parent: ramachandra.bhaskaram@wipro.com
0 siblings, 1 reply; 6+ messages in thread
From: Heikki Linnakangas @ 2007-01-16 10:13 UTC (permalink / raw)
To: ramachandra.bhaskaram@wipro.com; +Cc: pgsql-performance
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Caching in PostgreSQL
@ 2007-01-16 10:29 David Levy <dvid.levy@gmail.com>
parent: Heikki Linnakangas <heikki@enterprisedb.com>
0 siblings, 0 replies; 6+ messages in thread
From: David Levy @ 2007-01-16 10:29 UTC (permalink / raw)
To: Heikki Linnakangas <heikki@enterprisedb.com>; +Cc: ramachandra.bhaskaram@wipro.com; 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@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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Caching in PostgreSQL
@ 2007-01-16 16:10 Chris Browne <cbbrowne@acm.org>
parent: ramachandra.bhaskaram@wipro.com
1 sibling, 0 replies; 6+ messages in thread
From: Chris Browne @ 2007-01-16 16:10 UTC (permalink / raw)
To: pgsql-performance
ramachandra.bhaskaram@wipro.com writes:
> Can anybody tell me how can I implement data Caching in the
> shared memory using PostgreSQL.
PostgreSQL already does that.
Implementing this functionality is rather tricky: Between version 7.4
and now, it has seen *massive* change which has required a great deal
of effort on the part of various developers.
Reimplementing it without a well-tested, well-thought-out alternative
proposal isn't likely to happen...
--
let name="cbbrowne" and tld="linuxfinances.info" in name ^ "@" ^ tld;;
http://linuxfinances.info/info/emacs.html
"Just because it's free doesn't mean you can afford it." -- Unknown
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2007-01-16 16:10 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-01-16 08:43 Caching in PostgreSQL ramachandra.bhaskaram@wipro.com
2007-01-16 09:33 ` Heikki Linnakangas <heikki@enterprisedb.com>
2007-01-16 16:10 ` Chris Browne <cbbrowne@acm.org>
2007-01-16 09:43 Re: Caching in PostgreSQL ramachandra.bhaskaram@wipro.com
2007-01-16 10:13 ` Heikki Linnakangas <heikki@enterprisedb.com>
2007-01-16 10:29 ` David Levy <dvid.levy@gmail.com>
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