Duan Ligong wrote: > Would you like to be so kind as to answer the following questions: > > - Is there any way to control the number of clog files and xlog files? > I encounter an issue that there are too many clog files under the > pg_clog/ directory which occupy more space than I can endure.. pg_clog files are controlled by tuple freezing, which is done by vacuum, and it depends on the autovacuum_min_freeze_age parameter and vacuum_freeze_min_age. Please read http://www.postgresql.org/docs/8.3/interactive/routine-vacuuming.html and http://www.postgresql.org/docs/8.3/interactive/runtime-config-client.html#GUC-VACUUM-FREEZE-MIN-AGE > - What determines the number of clog files? what determines the > number of xlog files? The number of xlog files will depend on checkpoints. You need to restrict checkpoint_segments to control this. Note that this can have a serious performance impact. > - I understand pg_xlog is used to record WAL. but what is pg_clog > is used to? Is it used to record some meta-information on the xlog? clog is the "commit log", i.e. it records transactions that have been committed and those that have been aborted. You cannot delete files unless you want to corrupt your database. > - What effect does Deleting the clog and xlogfiles bring about? > Will it cause Postgresql abnormal stopping? Your data will be corrupt. It may continue to work for a while, and suddenly stop working at a future time. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
