2012/5/13 Robert Klemme <shortcutter@xxxxxxxxxxxxxx>
On Sun, May 13, 2012 at 10:12 AM, Віталій Тимчишин <tivv00@xxxxxxxxx> wrote:
> 2012/5/11 Robert Klemme <shortcutter@xxxxxxxxxxxxxx>
>> On the contrary: what would be the /advantage/ of being able to createI can almost see the point. But my natural choice in that case would
>> millions of sequences? What's the use case?
>
> We are using sequences as statistics counters - they produce almost no
> performance impact and we can tolerate it's non-transactional nature. I can
> imaging someone who wants to have a sequence per user or other relation
> row.
be a table with two columns. Would that actually be so much less
efficient? Of course you'd have fully transactional behavior and thus
locking.
We've had concurrency problems with table solution (a counter that is updated by many concurrent queries), so we traded transactionality for speed. We are actually using this data to graph pretty graphs in nagios, so it's quite OK. But we have only ~10 sequences, not millions :)
Best regards,
Vitalii Tymchyshyn
