Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

How to Reduce Disk Space Occupied by CUBRID


Disk space is always important to optimize. CUBRID comes with a highly customizable configuration file, which you can adjust to satisfy almost all needs.

We will give you now a few tips that will help you minimize the disk space occupied by the CUBRID databases:

  • Reduce db_volume_size and log_volume_size from their default 512M value to a smaller value of your convenience such as 100M or even 50M. Each time this amount is exceeded, a new file will be created. The time loss to create the files is rather small and the only disadvantage of taking this approach is that more files will be created.
  • Set log_max_archives to 0. This value limits the number of log archives created. You can set this value from 0 to INT_MAX, but the actual number of archives can exceed this value temporarily, while the system uses the log files. When they are no longer used, all unused archives exceeding this limit are erased. Thus, disk space is freed. The downside of limiting this value is reducing the ability of point-in-time restore which is based on these log archives.
  • Erase unnecessary archive logs by backing up the database with cubrid backupdb -r. More information can be found in the Database Backup manual page. 

Note: To add a parameter to cubrid.conf just place on a new line the name of the parameter followed by equal sign (=), followed by the value. Don't put any spaces between the parameter name, the equal sign or the value. Here is an example of lines that can be added to cubrid.conf:

log_max_archives=0
force_remove_log_archives=yes
comments powered by Disqus
Page info
viewed 2265 times
translations en
Author
posted 2 years ago by
CUBRID
Contributors
updated 2 years ago by
View revisions
Share this article