Currently, the only to do that is to dump the data and recreate another instance using that. For performance reasons we don't use innodb_file_per_table and, sadly, Innodb never shrinks the default tablespace.
-- Razvan ME
On Thu, Oct 31, 2013 at 6:40 AM, T.R. <tr@firespotter.com> wrote:
According to information schema I'm using less than 10 gig of space after dropping a 80+ gig table.--However the console shows disk usage at 97 gig.The large table I dropped was over 12 hours ago.Is there some way to reclaim space?Thanks,T.R.
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/7c48933b-d9f8-47e3-b8bb-3bf621c3fcfc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CA%2BUvTg0Qq6YB_i3xmb6N4GwzvmSzqpBvfVUyS7c4joWLR54h2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment