Hi,
I have gained a great experience by looking into the jdbc logs, but
unfortunately I haven't come to a conclusion yet. I need information
about the state of the mserver5 as well. For example, by looking only
the jdbc logs it is not clear when a transaction is commited.
Concerning the different monet_*.log files created by jdbc, should I
suppose that belong to a different jdbc thread, different transaction,
or something else?
And one last question: what are the debug options for mserver5? I
found this link
(http://monetdb.cwi.nl/MonetDB4-compiled/etc/MonetDB.conf) which
states a bunch of gdk_debug options some of them still valid in
monetdb5, but the one that I am interested in does not produce any
output (transaction management). Is there any alternative
value/property for transaction management? I am also aware of the
sql_debug (valid values 0/1). Other?
Thanks,
Babis
On Fri, Apr 8, 2011 at 3:03 PM, Fabian Groffen
On 08-04-2011 15:00:53 +0300, Charalampos Nikolaou wrote:
That was very helpful Fabian. Actually, there are 6 such log files. The next question concerns serialization. Does it suffice to grep all TX lines and sort them according to the id present next to TX? Have
yes
you got anything else to suggest in order to come to a conclusion about concurrency conflicts. In such a case, what would the solution be (actually, I have the answer, but I don't even want to spell it out)?
nothing other than carefully constructing the flow of events to see when MonetDB thinks a concurrency conflict occurs, then to verify if it is correct or not
------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users