Subject | Read Only Transactions |
---|---|
Author | Guido Klapperich |
Post date | 2006-09-05T21:43:07Z |
I have some questions concerning read only transactions. I have read the
article 'Understanding Interbase Transaction' from Bill Todd
(http://bdn1.borland.com/borcon2004/article/paper/0,1963,32280,00.html).
He said: Read only transactions consume less overhead and, in the case
of read committed read only transactions, do not inhibit garbage
collection. Not interfering with garbage collection can lead to better
performance. If you do not need to make changes to the database you
should always make your transaction read only.
Ann Harrison said in
(http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_expert4):
Every transaction participates in garbage collection - every
transaction, including read-only transactions.
Which statement is correct?
BTW, Bill said: A read only read committed transaction can remain open
indefinitely without causing the OAT to stick.
Is this right?
Regards
Guido
article 'Understanding Interbase Transaction' from Bill Todd
(http://bdn1.borland.com/borcon2004/article/paper/0,1963,32280,00.html).
He said: Read only transactions consume less overhead and, in the case
of read committed read only transactions, do not inhibit garbage
collection. Not interfering with garbage collection can lead to better
performance. If you do not need to make changes to the database you
should always make your transaction read only.
Ann Harrison said in
(http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_expert4):
Every transaction participates in garbage collection - every
transaction, including read-only transactions.
Which statement is correct?
BTW, Bill said: A read only read committed transaction can remain open
indefinitely without causing the OAT to stick.
Is this right?
Regards
Guido