Skip to content

Do not manage fact_values table in PuppetDB in PE 2017.2+ #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 19, 2017

Conversation

npwalker
Copy link
Contributor

PuppetDB refactored the way facts are stored in PE 2017.2 and as
a result the fact_values table no longer exists and does not
need more aggressive autovacuuming.

Since the fact values are now inlined in the facts table, the
facts table might warrant some monitoring.

Resolves #5

npwalker added 2 commits June 19, 2017 07:55
PuppetDB refactored the way facts are stored in PE 2017.2 and as
a result the fact_values table no longer exists and does not
need more aggressive autovacuuming.

Since the fact values are now inlined in the facts table, the
facts table might warrant some monitoring.

Resolves #5
@npwalker npwalker merged commit 158069d into master Jun 19, 2017
@npwalker npwalker deleted the dont_modify_fact_values_20172 branch January 7, 2019 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants