Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
| От | A.M. |
|---|---|
| Тема | Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" |
| Дата | |
| Msg-id | E03A51A8-4E4E-4975-A05F-AACB9791E326@themactionfaction.com обсуждение исходный текст |
| Ответ на | Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" ("C. Bergström" <cbergstrom@netsyncro.com>) |
| Ответы |
Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
|
| Список | pgsql-performance |
On Apr 3, 2007, at 15:39 , C. Bergström wrote: > A.M. wrote: >> 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.) > Not exactly what you're looking for and a simple API, but the > performance is very nice and has a lot of potential. > > http://pgfoundry.org/projects/pgmemcache/ I would like to use transactional semantics over tables that can disappear whenever the server fails. memcached does not offer that. Cheers, M
В списке pgsql-performance по дате отправления: