From: ktm@rice.edu <ktm@rice.edu>
To: Campbell, Lance <lance@illinois.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Enhancement Request
Date: Tue, 4 Mar 2014 09:59:10 -0600
Message-ID: <20140304155910.GA1150@aart.rice.edu> (raw)
In-Reply-To: <B75CD08C73BD3543B97E4EF3964B7D701F79BDF8@CITESMBX1.ad.uillinois.edu>
References: <B75CD08C73BD3543B97E4EF3964B7D701F79BDF8@CITESMBX1.ad.uillinois.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Tue, Mar 04, 2014 at 02:49:32PM +0000, Campbell, Lance wrote:
> Web Services at the University of Illinois has been using PostgreSQL for 11 years for serving up web content. We generate around two million pages of database driven content a month. We love the work you are doing.
>
> I have an enhancement request. Sometimes when using a database there is a need to have particular tables always in memory. An example of this would be our web application session data. The session data is used by a cluster of tomcat nodes. It would be nice to have a way to say to PostgreSQL, put this particular table data in memory always. If you already have this feature please let me know. There would probably also need to be a way to see how much data is being taken up by these preferred tables. This would probably require other things to also be put into memory as well like indexes.
>
> To get around this issue we are planning on implementing a second PostgreSQL database on a dedicated server in order to make sure the session data is always in memory. But it would be nice to not actually have a second server for just session data if we really don't need it.
>
> Thanks for considering this idea.
>
Hi Lance,
You might also want to take a look at pgmemcache:
http://pgfoundry.org/projects/pgmemcache/
It is a PostgreSQL interface to memcached which seems like it would fit your
needs for session data very well. The other option that was already mentioned
is to make a tmpfs tablespace.
Regards,
Ken
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: ktm@rice.edu, lance@illinois.edu
Subject: Re: Enhancement Request
In-Reply-To: <20140304155910.GA1150@aart.rice.edu>
* 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