On Tue, 20 Nov 2018 16:34:58 -0600 Dimitri Maziuk via Bacula-users wrote: > I've 320MB on a server that replicates a database of > a few million rows, and ~100MB on our bacula server > w/ a year's worth of backups. What do you call "too > big"?
As shared in the first message: Right now, even after drop_bacula_tables and no other databases (except what psql has as default after installation) I have: $ du -hs /var/lib/pgsql/data/pg_wal/ 769M /var/lib/pgsql/data/pg_wal/ That is for an empty bacula database. Those WAL files seem to be something like a "history" for what has been done during my tests: dropping tables, importing catalog, dropping again etc. The actual data which was used during those imports and drops (also shared in my first message): # du -hs bacula-backup.sql 63M bacula-backup.sql > There is wal_keep_segments: > https://www.postgresql.org/docs/10/runtime-config-replication.html > but if replication is not on, it's normally only a > handful of 16MB files in there, like 6 or so. Right now there are 52 files like those. I am not creating a super big enterprise system, so replication is not what I am looking for. On the link I read wal_keep_segments "Specifies the *minimum* number of past log file segments kept in the pg_wal directory". Isn't there a setting which controls the *maximum* number/volume/retention of those files? (like in a log rotation) -- George _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
