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 newer version of Postgres for Optimize performance tests #4665

Open
1 task
RomanJRW opened this issue Sep 27, 2024 · 2 comments
Open
1 task

Use newer version of Postgres for Optimize performance tests #4665

RomanJRW opened this issue Sep 27, 2024 · 2 comments
Assignees
Labels
scope:optimize Changes to Optimize. type:task Issues that are a change to the project that is neither a feature nor a bug fix. version:optimize 3.15.0

Comments

@RomanJRW
Copy link
Contributor

RomanJRW commented Sep 27, 2024

Acceptance Criteria (Required on creation)

Optimize runs its performance CI tests against an Engine with a Postgres version that is not in extended support

Hints

As per the conversation in this thread, Optimize is currently running its nightly performance tests against a provisioned Postgres instance using version 9. This version will soon go into extended support (in 2025), and incur higher costs.

Optimize should update to a newer version of Postgres with the connected engine. Note that the Postgres client is already the latest version, and the use of postgres is limited to storing engine data. It is expected to be a relatively straightforward migration with respect to breaking changes.

We first need to verify that these tests are successful when running against a new version of Postgres, then can update the version being used in GCP.

Links

Breakdown

Pull Requests

No tasks being tracked yet.

Dev2QA handover

  • Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment
@RomanJRW RomanJRW added type:task Issues that are a change to the project that is neither a feature nor a bug fix. scope:optimize Changes to Optimize. labels Sep 27, 2024
@yanavasileva
Copy link
Member

I am interested to work on this. And as far as I understand the priority is low.

@clementnero
Copy link

I am interested to work on this. And as far as I understand the priority is low.

Yes, this is not urgent as the final deprecation of PostgreSQL 9.6 is scheduled for 2028, but costs will increase between now and then.

When the newer version of PostgreSQL is chosen/known , please contact us so we can plan the migration on our end (or simply create a new ticket with a due date).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:optimize Changes to Optimize. type:task Issues that are a change to the project that is neither a feature nor a bug fix. version:optimize 3.15.0
Projects
None yet
Development

No branches or pull requests

3 participants