PostgreSQL backend: make powerdns a database owner #173
+6
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setup
Why?
I faced permissions issue that leads to:
I've fixed it manually by doing these queries:
Then I diged dipper to find how to puppetize them and came to that solution (making powerdns user an owner of powerdns db).
If it looks dangerous it may be fixed by adding these resources:
Details
pdns
can't start:Because puppet keeps trying to load SQL with schema on every run:
But it can't as I can see:
Trying to load schema dump manually from powerdns user:
OK, now I do the same as postgres user and it works:
But
pdns
can't start again because of insufficient priviledges:I'm not a PostgreSQL ninja but I duckduckgo'ed a solution that I mentioned above and look like it's somethin new at PostgreSQL 16 or so. Making powerdns user an owner of database works as well.