Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL as a local in-memory cache

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: jd(at)commandprompt(dot)com
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PostgreSQL as a local in-memory cache
Date: 2010-06-24 20:01:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
2010/6/24 Joshua D. Drake <jd(at)commandprompt(dot)com>:
> On Thu, 2010-06-24 at 21:14 +0200, Pavel Stehule wrote:
>> 2010/6/24 Josh Berkus <josh(at)agliodbs(dot)com>:
>> >
>> >> And I'm also planning to implement unlogged tables, which have the
>> >> same contents for all sessions but are not WAL-logged (and are
>> >> truncated on startup).
>> this is similar MySQL's memory tables. Personally, I don't see any
>> practical sense do same work on PostgreSQL now, when memcached exists.
> Because memcache is yet another layer and increases overhead to the
> application developers by adding yet another layer to work with. Non
> logged tables would rock.

I see only one positive point - it can help to people with broken
design application with migration to PostgreSQL.

There are different interesting feature - cached procedure's results
like Oracle 11. - it's more general.

only idea.

For me memory tables are nonsens, but what about memory cached
materialised views (maybe periodically refreshed)?



> SELECT * FROM foo;
> :D

> JD
> --
> Major Contributor
> Command Prompt, Inc: - 509.416.6579
> Consulting, Training, Support, Custom Development, Engineering

In response to


pgsql-performance by date

Next:From: A.M.Date: 2010-06-24 20:38:45
Subject: Re: PostgreSQL as a local in-memory cache
Previous:From: Joshua D. DrakeDate: 2010-06-24 19:47:46
Subject: Re: PostgreSQL as a local in-memory cache

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group