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

Use PGO by Default #84

Merged
merged 1 commit into from
Jun 16, 2024
Merged

Use PGO by Default #84

merged 1 commit into from
Jun 16, 2024

Conversation

ranchodeluxe
Copy link
Contributor

@ranchodeluxe ranchodeluxe commented Jun 6, 2024

By default use Crunchdata Postgresql Operator

Addresses #77

@ranchodeluxe ranchodeluxe requested review from sunu and ividito June 7, 2024 22:48
@ranchodeluxe ranchodeluxe changed the title WIP: Use PGO Use PGO by Default Jun 7, 2024
@ranchodeluxe
Copy link
Contributor Author

@sunu and @ividito: given some of the ticketing AC in #77 wondering if we should scope out another postgres HA operator? You two have any comments or thoughts about that? The issue around resource finalization and deletion from PGO interference is real and I will ticket anyhow

Screen Shot 2024-06-09 at 9 34 25 AM

@ranchodeluxe ranchodeluxe merged commit e7e05a4 into main Jun 16, 2024
2 checks passed
@j08lue j08lue deleted the gc/crunchy_pgo branch October 7, 2024 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant