http://forums.enterprisedb.com/posts/list/8.page JForum - http://www.jforum.net
Truncating in GridSQL is taking lot of time even for very minimum number of rows.

Thanx
]]> http://forums.enterprisedb.com/posts/preList/1384/4924.page http://forums.enterprisedb.com/posts/preList/1384/4924.page GMT
Does this eventually return?

There really is no magic going on here, GridSQL simply passes the TRUNCATE command down to all of the nodes that the table is partitioned on. I am not sure why it would take longer.

Thanks,

Mason]]> http://forums.enterprisedb.com/posts/preList/1384/4928.page http://forums.enterprisedb.com/posts/preList/1384/4928.page GMT
Thanks for the reply,

But the table containing only 5 to 10 rows in a table which is non partitioned also taking lots of time and finally there is no result.
Is there any place like log file to check where it is getting choked.

Thanks]]> http://forums.enterprisedb.com/posts/preList/1384/4929.page http://forums.enterprisedb.com/posts/preList/1384/4929.page GMT
This is working for me:

gstest2=> create table trunctest (col1 int, col2 int) on node 1;
OK
gstest2=> insert into trunctest values (1, 2);
INSERT 0 1
gstest2=> insert into trunctest values (3, 4);
INSERT 0 1
gstest2=> truncate trunctest;
OK

Note that truncating requires an exclusive lock on the table.

If I start another session, do a begin work, and insert, and in a separate session try and truncate, the truncate will appear to hang, because it cannot get an exclusive lock. I am guessing that the table is probably being used in another session(?).

Regards,

Mason


]]> http://forums.enterprisedb.com/posts/preList/1384/4931.page http://forums.enterprisedb.com/posts/preList/1384/4931.page GMT