> On 26 Mar 2017, at 08:04, Manish gupta <gahoimnshg@gmail.com> wrote:
>
> OK,
> I got there is no vacuum cleaning algo implemented yet.
> https://www.monetdb.org/Documentation/Manuals/ SQLreference/Transactions
>
> Would drop the records after ascii dump and recreate table.
You can also temporarily store the data of the <table to be cleaned> in a <backup table>.
Then do a “delete from <table to be cleaned>”, which simply wipe out all data, incl. garbage from <table to be cleaned>.
Finally, put all data from <backup table> back to <table to be cleaned>.
This is mostly probably (much) faster than an ASCII dump and restore.
>
> Regards,
> Manish
>
> On Sat, Mar 25, 2017 at 5:25 PM, Manish gupta <gahoimnshg@gmail.com> wrote:
> The problem is that I am having ~70M rows in a table, but its bat storage size is showing 170M rows. Although the count * still returns 70M, but memory is increasing very heavy each day. As described in previous mail, each day, ~1M rows are deleted from table and ~1.1M added, but it actually increases the size by 1.1M.
> Please let me know if something wrong in this way of updation of monetDB tables.
>
> Regards,
> manish
>
> On Sat, Mar 25, 2017 at 2:05 PM, Manish gupta <gahoimnshg@gmail.com> wrote:
> Dear All,
> Is there a way to truncate the table size when deleting some of the records? In my application, I delete and insert ~1 million records daily. But effectively, it should result in few hundreds additional records. But, I see the size of the table increases by a millions ( that can be seen in storage(), as well as hard disk size ). While the "select count(*) from table" reflects correct number. Is there a way, I can stop increase in table size in my scheme?
>
>
> Regards,
> Manish
>
>
> _______________________________________________
> users-list mailing list
> users-list@monetdb.org
> https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________
users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list