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

2015-12-24 Thread Ann Harrison aharri...@ibphoenix.com [firebird-support]
On Thu, Dec 24, 2015 at 1:03 PM, Dmitry Yemanov dim...@users.sourceforge.net [firebird-support] wrote: > 24.12.2015 05:31, 'Leyne, Sean' wrote: > > > > With today's unlimited availability of disk space and silly-low cost per > GB for storage, would an argument

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

2015-12-24 Thread Dmitry Yemanov dim...@users.sourceforge.net [firebird-support]
24.12.2015 05:31, 'Leyne, Sean' wrote: > > With today's unlimited availability of disk space and silly-low cost per GB > for storage, would an argument to dispense with the delta and simply store a > full copy of the record (not including BLOB) be worthy of discussion? It's not about storage

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

2015-12-23 Thread Dmitry Yemanov dim...@users.sourceforge.net [firebird-support]
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

2015-12-23 Thread 'Leyne, Sean' s...@broadviewsoftware.com [firebird-support]
> 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] Re: UPDATE to same record causing heavy disk I/O

2015-12-23 Thread Ann Harrison aharri...@ibphoenix.com [firebird-support]
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