Skip to content
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

Cannot remove pgaudit from default installations #3967

Open
Leo791 opened this issue Aug 13, 2024 · 3 comments
Open

Cannot remove pgaudit from default installations #3967

Leo791 opened this issue Aug 13, 2024 · 3 comments

Comments

@Leo791
Copy link

Leo791 commented Aug 13, 2024

In one of our use cases we wish not to have the pgaudit extension enabled. So far, looking at the code base I have not found a way to do this.

pgaudit seems to be a mandatory property that cannot be removed for the install. However, dropping it afterwards does not seem to impact functionality of the instance.

Is there a way to remove pgaudit from the mandatory parameters? Or is there a reason it is being handled as a mandatory parameter?

@tjmoore4
Copy link
Contributor

Hi @Leo791. You are correct that, by default, pgAudit is installed during cluster creation. The reasoning behind this is that, for those who would like to use pgAudit, it is easier to configure later without requiring any cluster downtime since it is already installed. The default configuration should not perform any logging and should incur almost no overhead, so we felt this was a reasonable default.

Given the above, could you provide more details for your use case and why you would prefer to not have pgAudit enabled?

@Leo791
Copy link
Author

Leo791 commented Aug 21, 2024

@tjmoore4 thank you for your answer, I'll try to explain the use case.

Our use case is a very basic service plan which doesn't allow for updates and should spend the minimum possible resources. So having pgaudit uninstalled would be a gain in overhead. However, as you say, minimal. Again, as you say, if we ever decide to allow updates to this service plan having pgaudit already there could be beneficial.

Currently we are disabling pgaudit post provisioning of the custom resource and this works for us. So this is a non-issue on our side. I opened this thread to better understand the reasoning behind this decision, which you have now provided.

@tjmoore4
Copy link
Contributor

@Leo791 thank you for that information. I'm glad to hear it's not causing any issues on your side. If you have any other questions regarding pgAudit, please let me know. Otherwise, I will plan to close out this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants