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

Поиск
Список
Период
Сортировка
От Arnau
Тема Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Дата
Msg-id 461366E8.90906@andromeiberica.com
обсуждение исходный текст
Ответ на Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"  (Ansgar -59cobalt- Wiechers <lists@planetcobalt.net>)
Список pgsql-performance
Hi Josh,

Josh Berkus wrote:
> Arnau,
>
>> Is there anything similar in PostgreSQL? The idea behind this is how I
>> can do in PostgreSQL to have tables where I can query on them very often
>> something like every few seconds and get results very fast without
>> overloading the postmaster.
>
> If you're only querying the tables every few seconds, then you don't
> really need to worry about performance.

Well, the idea behind this is to have events tables, and a monitoring
system polls that table every few seconds.  I'd like to have a kind of
FIFO stack. From "the events producer" point of view he'll be pushing
rows into that table, when it's filled the oldest one will be removed to
leave room to the newest one. From "the consumer" point of view he'll
read all the contents of that table.

So I'll not only querying the tables, I'll need to also modify that tables.


--
Arnau

В списке pgsql-performance по дате отправления:

Предыдущее
От: Ron Mayer
Дата:
Сообщение: Re: SCSI vs SATA
Следующее
От: "Peter Kovacs"
Дата:
Сообщение: Re: SCSI vs SATA