> Hi,
>
>
> does no one have an idea?
>
> It may be a rare case doing the same UPDATE a thousand times. But I´m really
> interested why this is not happening when doing DIFFERENT updates. And, of
> course, if something could be done on the database side to prevent this
> behavior in case so
Hi
it is side effect of MVCC implementation of Postgres. There is not possible
vacuum inside open transaction.
If you need it, then you should to use a different database - Postgres
doesn't work well when one record is highly often used in transaction.
Usual solution for Postgres is some proxy, t
Hi,
does no one have an idea?
It may be a rare case doing the same UPDATE a thousand times. But I´m really
interested why this is not happening when doing DIFFERENT updates. And, of
course, if something could be done on the database side to prevent this
behavior in case some application dev
Hi,
we recently found a bug in one of our applications which was doing exactly the
same UPDATE operation a few thousand times inside a transaction. This caused
the UPDATEs to become slower and slower from some milliseconds to some seconds.
We already fixed the application but I am wondering i
