-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Could this be bug 3474 [1]? This bug is fixed in the Oct2014 branch, but it requires recreating multi-column constraints. We will do that during the upgrade, but if there are duplicates, manual intervention will be needed (somebody will have to fix the duplicate keys). [1] https://www.monetdb.org/bugzilla/show_bug.cgi?id=3474 On 22/10/14 10:48, Pierre-Adrien Coustillas wrote:
Hello,
(google translate)
We had a crash monetdb following a full disk. We had already found that the bug not uniq table (corrupt catalog) could be related to these crash. And indeed this command will return no rows before the crash, but 20 lines after the crash : echo "SELECT name FROM SYS.TABLES WHERE system=false;" | mclient base | grep " " | grep -v " name " | grep -v " tuple" | sed 's/[| ]//g' | sort | uniq -c | grep -v " 1 " 5 bdm__lm__agregats 4 bdm__lm__agregats_temp 5 bdm__tra__agregats 4 bdm__tra__agregats_temp 5 ci__data__agregats 6 ci__data__reporting .. ... ...
Is the October 2014 release will fix this trouble? We are Jan2014-SP3
Pierre
-- 1G6 52 route de bischwiller 67300 Schiltigheim Société de Services et de Formations en Logiciels Libres http://1g6.biz Tél : 06 64 63 70 35
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
- -- Sjoerd Mullender -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQCVAwUBVEd8Jz7g04AjvIQpAQJAwwP9HDefykbPzxAwH02WHnpMqxRgZJWtlb2j SdAIeSCYD+z6tx+RXVOG0u/ChqfCjvM/oiLPiuvEbDoKgjo4fG1DMJ5Ode30MYqq u4cKfbcKihHYVR1fp4ddBJcCZ1Ot/4y/4KEPIOBXYlWgseW2V4ozwU5SXTjoDY8W Z761AEDO/Ho= =grTT -----END PGP SIGNATURE-----