On Mon, 24 May 2004, David Garamond wrote:
> Manfred Koizar wrote:
> > You mean InnoDB cannot handle the load?
>
> Perhaps it's more appropriate to say that the disk becomes the bottleneck.
Was this attempting to do each update in a separate transaction?
If so, that is certainly expected, with whatever disk based transactional
database you use. With innodb, you could hack around it by configuring
innodb not to flush its log to disk at every transaction, obviously at
the risk of loosing data if something crashes.
>From what I have seen, I would expect innodb's multiversioning to work
better for the use you describe than postgresql's due how it implements
undo logs for updates. However, there could well be other differences
that could make postgresql work better for your application depending on
exactly what issues you are seeing.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
