Postgres Pro
Downloads
Home   >   mailing lists

Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" - Mailing list pgsql-performance

From A.M.
Subject Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date
Msg-id EE4A4157-6E35-4DEC-B257-D08F1102F224@themactionfaction.com
Whole thread Raw
In response to Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
List pgsql-performance
Tree view 
Indeed... I looked through the official TODO list and was unable to
find an entry for global temporary tables- such a thing would be
ideal for any transient data such as web sessions or materialized
views. Is there any reason why global temp tables shouldn't be
implemented? (And, no, I'm not simply referring to "in-memory"
tables- they can simply be handled with a ram disk.)

-M

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Next
From: Erik Jones
Date:
Subject: Re: Shared buffers, db transactions commited, and write IO on Solaris