or could it be changed to read-only in FB4?
It is meaningless. Read-write transaction has no differences from
read-only until it perform an actual write.
And no, it cannot be "read-only read committed" for the consistency
sake.
Also notice that RO-RC lost it's magic in FB4: long running
tranactions do not prevent intermediate GC.
Thanks for you answers, but you are answering question I did not ask :)
I was talking abou read-write/read-only flag, nothing else. Why?
Some of our customers do a lot of data processing overnight, and some
tasks require that all work from previous day is finished.
For this reason I am testing in monitoring tables whether there is
active read-write transaction with yesterdays or older timestamp.
And sometimes it happens that they start backup before midnight and it
finishes after midnight and thus it blocks some processing.
(I could test MON$REMOTE_PROCESS whether is is null or contains
gbak.exe, I just do not like hardcoding process name in query)
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
