There is indeed a problem (server crash) when doing this. However, there is no point in creating an ordered index and then appending to a column: the ordered index necessarily has to be removed when the table is changed. This is because the index contains ordering information on the column which changes in such a way that the index cannot be maintained.
On 03/11/2019 04.35, lhy1149 wrote:
Hello,
I don't know if it's appropriate, but because I can't register monetdb's bugzilla, I'm going to report a bug here. This problem causes the insert statement to hang and mserver5 takes up 100% of the CPU time. Here is the code that caused the problem:
Create table a(a int, b int, id bigserial);
-- comment any of the next 2 lines will resolve the problem Create ordered index a_pk on a(id); Create index a_idx1 on a(a);
Insert into a(a) values(1); -- this line will hang
Enviroment: macOS Catalina 10.15 MonetDB v11.33.11
I hope the development team can check if there is this problem.
Thank you _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list