tag:blogger.com,1999:blog-21750032212925164852012-01-16T11:11:44.243-08:00Unknownhttp://www.blogger.com/profile/08719199755892344785noreply@blogger.comBlogger11100tag:blogger.com,1999:blog-2175003221292516485.post-50015921667485278972011-12-14T17:00:00.001-08:002011-12-15T06:22:49.295-08:00A quick, but I hope interesting note: the commit operation in Oracle database is very fast (actually oracle is doing a fast commit), as opossed to rollback, which may take as long as the operation that is being rolled back. Thinking of it, before comitting, most of the work is done already, except for writing the dirty buffers to disk and the information to redo logs, while the rollback has to read data back from the disk (UNDO tablespace) and apply it to the data files. So oracle is having an optimistic approach and I guess they are right, most of the time the changes are comitted, rather than rolled back.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2175003221292516485-5001592166748527897?l=florin-m.blogspot.com' alt='' /></div>Unknownhttp://www.blogger.com/profile/08719199755892344785noreply@blogger.com0