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

[Enhancement] Remove postgres from GVM. #237

Open
rudnypc opened this issue Jul 26, 2021 · 4 comments
Open

[Enhancement] Remove postgres from GVM. #237

rudnypc opened this issue Jul 26, 2021 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@rudnypc
Copy link

rudnypc commented Jul 26, 2021

It would be nice to have a separate postgres and GVM container.

@rudnypc rudnypc changed the title [Enhancement Remove postgres from GVM. [Enhancement Remove postgres from GVM.] Jul 26, 2021
@rudnypc rudnypc changed the title [Enhancement Remove postgres from GVM.] [Enhancement] Remove postgres from GVM. Jul 26, 2021
@austinsonger
Copy link
Contributor

@rudnypc please describe the use case and how this would benefit the community.

@rudnypc
Copy link
Author

rudnypc commented Jul 27, 2021

Some companies have a cluster of databases or databases as services.
We also have a number of other benefits.

@Dexus Dexus added the enhancement New feature or request label Sep 29, 2021
@Dexus
Copy link
Contributor

Dexus commented Sep 29, 2021

I think we can make it happen, but the main problem will be that the binaries will only get the headers for the current supported postgres of the container, so if you run different postgres versions you can run into truble.

So all in all, we can make the postgres optional, but then we will not support anything that will have todo with postgres and DB at all.

Is this worth it?

@schewara
Copy link

Hi. To add some additional info from my perspective.

We are running a standardized PostgreSQL Container Setup which includes all the monitoring, backup, restore scripts and utilities.
For example, we're using pgBackRest backing up the DB to S3 and getting this functionality into the current setup would be quite cumbersome.
For us it would also be a big benefit to be able to reuse this setup, instead of reinventing the wheel for some services.

The limitations on a specific PostgreSQL Version should be less of a problem (at least in our case) as long as it is documented somewhere.

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

No branches or pull requests

4 participants