Jira (PDB-3212) Vacuum reports after GC

[Ryan Senior (JIRA)]

Ryan Senior created an issue

PuppetDB / PDB-3212 Vacuum reports after GC Issue Type: New Feature Assignee: Unassigned Created: 2016/12/06 7:11 AM Priority: Normal Reporter: Ryan Senior On larger PuppetDB installs, garbage collecting reports can free a significant amount of space. Relying on autovacuuming of these tables can be troublesome. From a reports perspective, almost all of the garbage is generated from report GC. Waiting to vacuum increases the potential that another GC run will happen, increasing the amount of data to vacuum and prolonging the amount of time autovacuuming takes. Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Ryan Senior (JIRA)]

Ryan Senior updated an issue

PuppetDB / PDB-3212 Vacuum reports after GC

Change By: Ryan Senior Sprint: Hopper

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-3212 Vacuum reports after GC

Change By: Russell Mull Sprint: Hopper

Add Comment

[Jeff Yarnell (JIRA)]

Jeff Yarnell updated an issue

PuppetDB / PDB-3212 Vacuum reports after GC

Moving this from Hopper to Backlog because...easy workaround used today in the field.

Add Comment

[Jeff Yarnell (JIRA)]

Jeff Yarnell updated an issue

PuppetDB / PDB-3212 Vacuum reports after GC

Change By: Jeff Yarnell Sprint: Hopper/Triage

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

PuppetDB / PDB-3212 Vacuum reports after GC

Change By: Claudia Petty Labels: new-feature

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)