Ok i'm going to have a look. So for now it is best to downgrade to the previous version of the monetdb packages, or will there be fixed packages released for this soon? thanks, - Gijs On 05/04/2012 01:40 PM, Sjoerd Mullender wrote:
See changeset bb296c17ead0 for the fix.
On 2012-05-04 11:40, Gijs Molenaar wrote:
On 05/04/2012 01:12 AM, Stefan Manegold wrote:
Hm, looks like a second client connection after an upgrade without restarting teh server tries to do the upgrade actions (e.g., adding new functions), again.
I did not test this with my upgrade tests, I only tested a second client connection after upgrading and restarting the server --- indeed a gap in my testing routine ...
Could you try to stop & restart your server and see whether the problem persists?
After a stop & start with monetdbd I still get the same error message while connecting with a client.