Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WKrkY-0004pm-As for pgsql-admin@arkaria.postgresql.org; Tue, 04 Mar 2014 15:59:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WKrkX-0003u4-J4 for pgsql-admin@arkaria.postgresql.org; Tue, 04 Mar 2014 15:59:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WKrkW-0003sG-1L for pgsql-admin@postgresql.org; Tue, 04 Mar 2014 15:59:20 +0000 Received: from proofpoint1.mail.rice.edu ([128.42.201.100] helo=pp1.rice.edu) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WKrkQ-0003XG-3y for pgsql-admin@postgresql.org; Tue, 04 Mar 2014 15:59:19 +0000 Received: from pps.filterd (pp1.rice.edu [127.0.0.1]) by pp1.rice.edu (8.14.5/8.14.5) with SMTP id s24Fve2v014745; Tue, 4 Mar 2014 09:59:10 -0600 Received: from mh1.mail.rice.edu (mh1.mail.rice.edu [128.42.201.20]) by pp1.rice.edu with ESMTP id 1jae181t6q-1; Tue, 04 Mar 2014 09:59:10 -0600 X-Virus-Scanned: by amavis-2.7.0 at mh1.mail.rice.edu, auth channel X-SMTP-Auth: no X-SMTP-Auth: no Received: from aart.rice.edu (aart.rice.edu [168.7.56.48]) by mh1.mail.rice.edu (Postfix) with ESMTP id 3F10B4601ED; Tue, 4 Mar 2014 09:59:10 -0600 (CST) Received: by aart.rice.edu (Postfix, from userid 18612) id 3567D1005F3; Tue, 4 Mar 2014 09:59:10 -0600 (CST) Date: Tue, 4 Mar 2014 09:59:10 -0600 From: "ktm@rice.edu" To: "Campbell, Lance" Cc: "pgsql-admin@postgresql.org" Subject: Re: Enhancement Request Message-ID: <20140304155910.GA1150@aart.rice.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-12-10) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.996772200306069 urlsuspect_oldscore=0.996772200306069 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=7269 rbsscore=0.996772200306069 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1403040071 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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