Quick Links

Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"

From:	Alan Hodgson <ahodgson(at)simkin(dot)ca>
To:	pgsql-performance(at)postgresql(dot)org
Subject:	Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date:	2007-04-03 20:00:45
Message-ID:	200704031300.46013@hal.medialogik.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-performance

On Tuesday 03 April 2007 12:47, "A.M." <agentm(at)themactionfaction(dot)com> wrote:
> On Apr 3, 2007, at 15:39 , C. Bergström wrote:
> I would like to use transactional semantics over tables that can
> disappear whenever the server fails. memcached does not offer that.

How would temporary tables?

--
Ginsberg's Theorem:
1) You can't win.
2) You can't break even.
3) You can't quit the game.

In response to

Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" at 2007-04-03 19:47:41 from A.M.

Responses

Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" at 2007-04-03 20:06:30 from A.M.

Browse pgsql-performance by date

	From	Date	Subject
Next Message	A.M.	2007-04-03 20:06:30	Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Previous Message	A.M.	2007-04-03 19:47:41	Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"