Re: update/insert,

> > Which is faster will probably depends on what is more common in your DB:
> > row already exists or not. If you know that 99% of the time the row
> > will exist, the update will probably be faster because you'll only
> > execute one query 99% of the time.
>
> OK, but the point of the question is that constantly updating a single row
> steadily degrades performance, would delete/insery also do the same?

Yes. Delete still creates a dead row. There are programatic ways around this
but keeping a delete table that can be truncated at intervals.

Joshua D. Drake

>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings