procedure to follow when changing the sql-optimizer settings
Hi, We were getting database crashes when we were using our database with read/write mode and using the default sql_optimizer settings. We decided to run our database in read-only mode and also has changed the sql_optimizer setting to sequential_pipe. With new settings we don't see any crashes but have started to see error messages in the log files similar to the following lines. 2014-04-25 08:21:52 ERR db1[14554]: #mvc_bind_schema schema1 2014-04-25 08:21:52 ERR db1[14554]: #mvc_bind_table schema1.table1 2014-04-25 08:21:52 ERR db1[14554]: #mvc_bind_column table1.col1 2014-04-25 08:21:52 ERR db1[14554]: #mvc_rollback 2014-04-25 08:21:52 ERR db1[14554]: #mvc_rollback done 2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit 2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit done My question is there a procedure to follow when we change sql-optimizer settings? I assume MonetDB has some history of the past and because of the change of the sql_optimizer settings the bits in the history causing these error messages but i would not be surprised if this is completely wrong. Mahmut Uludag
On 25/04/14 10:57, Mahmut Uludag wrote:
Hi, hi, What platform and which version are you using for MonetDB?
We were getting database crashes when we were using our database with read/write mode and using the default sql_optimizer settings. Could you provide the minimal query/data that elicits this effect? We decided to run our database in read-only mode and also has changed the sql_optimizer setting to sequential_pipe.
With new settings we don't see any crashes but have started to see error messages in the log files similar to the following lines.
2014-04-25 08:21:52 ERR db1[14554]: #mvc_bind_schema schema1 2014-04-25 08:21:52 ERR db1[14554]: #mvc_bind_table schema1.table1 2014-04-25 08:21:52 ERR db1[14554]: #mvc_bind_column table1.col1 2014-04-25 08:21:52 ERR db1[14554]: #mvc_rollback 2014-04-25 08:21:52 ERR db1[14554]: #mvc_rollback done 2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit 2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit done These are debugging statements and do not relate to optimizers. regards, Martin
My question is there a procedure to follow when we change sql-optimizer settings? I assume MonetDB has some history of the past and because of the change of the sql_optimizer settings the bits in the history causing these error messages but i would not be surprised if this is completely wrong.
Mahmut Uludag _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
Hi Martin,
What platform and which version are you using for MonetDB?
We use the latest Jan 2014-SP1 bugfix release but were getting the crashes with earlier releases as well. Databases run on GNU/Linux machines, x86_64.
We were getting database crashes when we were using our database with read/write mode and using the default sql_optimizer settings. Could you provide the minimal query/data that elicits this effect?
I apologise but we don't have resources to follow this.
2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit 2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit done These are debugging statements and do not relate to optimizers.
I remember we compiled the release using the default options. The "ERR" marks was little alarming especially when we first time saw the messages, we now understand they don't cause any harm. Is it possible to disable these debug messages? --mahmut
Hi Mahmut, I'm afraid the debug message are an unintended side-effect of running your database in read-only mode. We'll have to look into the code and find a fix to properly separate debug options from "feature" options. Best, Stefan ----- Original Message -----
Hi Martin,
What platform and which version are you using for MonetDB?
We use the latest Jan 2014-SP1 bugfix release but were getting the crashes with earlier releases as well. Databases run on GNU/Linux machines, x86_64.
We were getting database crashes when we were using our database with read/write mode and using the default sql_optimizer settings. Could you provide the minimal query/data that elicits this effect?
I apologise but we don't have resources to follow this.
2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit 2014-04-25 08:21:52 ERR db1[14554]: #mvc_commit done These are debugging statements and do not relate to optimizers.
I remember we compiled the release using the default options. The "ERR" marks was little alarming especially when we first time saw the messages, we now understand they don't cause any harm. Is it possible to disable these debug messages?
--mahmut _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
participants (3)
-
Mahmut Uludag -
Martin Kersten -
Stefan Manegold