Thank you very much for your answer Alexey, I was very bussy these days.
Looking at the page 46 it seems more understandable now.
Greetings.
Walter.
On Wed, Mar 25, 2015 at 2:02 PM, Alexey Kovyazin a...@ib-aid.com
[firebird-support] firebird-support@yahoogroups.com wrote:
Hi Walter,
On
Hi Walter,
I have just one doubt, and it is with page 46.
Do you mean Record versions visibility?
Regards,
Alexey
Hi Alexey
Yes, that's right, I can not understand well the page 46. I suppose that R1
means record version 1, R2 means record version 2, etc.
Tx16 did the INSERT?
Tx12 can do a COMMIT although it had started before Tx16 and Tx18 is still
active?
Tx25 can change what Tx14 did although Tx14 is
Hi Walter,
On slide 46 of http://www.slideshare.net/ibsurgeon/3-how-transactionswork
we consider how transaction 20 view record versions.
It's important to note that transaction 20 is a snapshot.
Tx16 did the INSERT?
Yes, it created original version of Record 1.
Tx12 can do a COMMIT although
Hello Alexey
Your presentation is an excellent work, as ever.
I had wrote an article in my blog about it:
https://firebird21.wordpress.com/2015/03/23/presentacion-sobre-transacciones-de-alexey-kovyazin/
You had explained very well everything and all can be easily understood.
Thank you very
Ok, many thanks.
Regarding the Awaiting GC issue I've done another test:
1- Connect to the database in a test environment, isolated from the rest of
users from production environment. with IBExpert or another database manager.
Only one connection.
2- Monitor tha database with Sinatica Monitor to get
Hi,
Unfortunately, your experiments are not useful at all, since you are
using complex GUI tools, which run background queries in the frames of
implicit transactions to get metadata information, etc.
If you really want to do clean experiments with Firebird transactions,
use only isql.exe, and
