Hey Anfield, prune_upto was retired before 2016.2, along with the console database itself (the data is in PuppetDB now). The way to control report deletion is via the node_ttl, node_purge_ttl, and report_ttl PuppetDB configuration settings, which are documented here: https://docs.puppet.com/puppetdb/latest/configure.html#node-ttl
The vacuum operations on the page you linked may be necessary if you start to run into performance issues resulting from database bloat, but they'll only clear dead tuples in the database; they won't delete data. My guess is you'll be fine with just the config settings, but you can read more about vacuum here if needed: https://www.postgresql.org/docs/9.4/static/sql-vacuum.html Wyatt On Thursday, February 16, 2017 at 1:41:11 PM UTC-8, Anfield wrote: > > For cleaning up report data is the parameter prune_upto still valid? - > related to version 2016.2 > > Or has the vacuum parameter replaced it? Do they both essentially do the > same thing? > > https://docs.puppet.com/pe/2016.2/maintain_console-db.html > > Thanks > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/494fb6ec-6cc5-44ba-a0df-3e07f28fb17b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
