Re: [PERFORM] Disabling transaction/outdated-tuple behaviour

2004-08-26 Thread Josh Berkus
Neil, > I am using a simple PostgreSQL 7.3 database in a soft-realtime > application. Then you're not going to like the answer I have for you, see below. > I have a problem where an update on a record within a (fully indexed) > table containing less than ten records needs to occur as fast as > p

Re: [PERFORM] Disabling transaction/outdated-tuple behaviour

2004-08-26 Thread Matt Clark
> Immediately after performing a vaccum, updates take upto 50 > milliseconds to occur, however the update performance > degrades over time, such that after a few hours of continuous > updates, each update takes about half a second. Regular > vacuuming improves the performance temporarily, but d

[PERFORM] Disabling transaction/outdated-tuple behaviour

2004-08-26 Thread Neil Cooper
I am using a simple PostgreSQL 7.3 database in a soft-realtime application. I have a problem where an update on a record within a (fully indexed) table containing less than ten records needs to occur as fast as possible. Immediately after performing a vaccum, updates take upto 50 milliseconds to