Feature #427
Updated by Madars almost 5 years ago
Currently tmqueue stores all messages on disk and in the same time in memory. New binary could be "tmqueuepq"
For some big queues, the memory might be too short, consuming all the server memory.
Thus we could implement so that the messages are stored in posgresql.
For each queue new db table could be created from source code. Or maybe single table. it depends on polling mechanism, or maybe configuration.
The locked messages which are in progress still we would like to keep in the memory hash.
For some big queues, the memory might be too short, consuming all the server memory.
Thus we could implement so that the messages are stored in posgresql.
For each queue new db table could be created from source code. Or maybe single table. it depends on polling mechanism, or maybe configuration.
The locked messages which are in progress still we would like to keep in the memory hash.