Re: [firebird-support] UPDATE to same record causing heavy disk I/O

Hi Caroline, It could be a chain of many record versions. If you have such database handy, run gstat -a -r > stat.txt and load it to HQbird Database Analyst (trial version will be enough), then open tab Tables and sort on Max Versions column. Check how many versions on the table you are

[firebird-support] Re: UPDATE to same record causing heavy disk I/O

23.12.2015 01:36, Ann Harrison wrote: > Like I said, I have always kept transactions very short. I am > thinking of something like this instead: > > a) begin a transaction, update FIELD_1 of MYTABLE. > b) update FIELD_2 of MYTABLE. > c) update FIELD_3 of MYTABLE. > d)

RE: [firebird-support] Re: UPDATE to same record causing heavy disk I/O

> Right. When we were working on InterBase 1.1 (I think) a friend of Jim's > suggested using deltas for back versions to save space.  He's still a friend, > but > that feature was a real trial to implement and debug, partly because we ran > out of bits in the record header. With today's

Re: [firebird-support] UPDATE to same record causing heavy disk I/O

On Wed, Dec 23, 2015 at 7:12 AM, Alexey Kovyazin a...@ib-aid.com [firebird-support] wrote: > > longest chain of versions here). > > If you will see a long chain of versions, it means that you are updating > the same record while some other writeable transaction

Re: [firebird-support] Re: UPDATE to same record causing heavy disk I/O

On Wed, Dec 23, 2015 at 12:01 PM, Dmitry Yemanov dim...@users.sourceforge.net [firebird-support] < firebird-support@yahoogroups.com> wrote: > 23.12.2015 01:36, Ann Harrison wrote: > > > > > ...Your first update will create a back > > version that's just the difference between the old record state