You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgreSQL major version 12 is being retired in February of 2025.
Actions
To avoid possible downtime and handle these database engine version upgrades during the most convenient time for your applications, please reply to cloud.gov support email to let them know which option we are selecting:
Heavily Recommended: Create a new db instance, migrate the data, test your application, delete the old db instance.
There is tooling provided at https://github.com/cloud-gov/cg-manage-rds which shows how to import and export brokered databases. Additional information for PostgreSQL version 15 can be found at https://www.postgresql.org/docs/15/release-15.html#id-1.11.6.13.4. Please note for PostgreSQL versions 15+ , using SSL is required when connecting to your database. As such, you will need to configure your client library to use SSL when connecting to your database.
Contact us and we will set the database instance to upgrade during the next maintenance window (Times are in UTC).
Contact us and we can schedule the upgrade during normal business hours.
Your database services that need to be upgraded are:
Org Space Instance name Engine Engine Version Maintenance Window (UTC)
gsa-18f-tock prod tockdb postgres 12.19 wed:11:06-wed:11:36
gsa-18f-tock staging tock-database postgres 12.19 sun:07:02-sun:07:32
The databases will be upgraded as per the upgrade path outlined in option #2, no earlier than February 10th, 2025 starting 12:00 AM (assuming you don’t choose to upgrade earlier) but please note that if a selection is not made by February 10th, your database engine version will be upgraded for you during the maintenance window.
There will be no increase in your Cloud.gov bill associated with these RDS PostgreSQL engine version upgrades. Currently, pricing for databases on Cloud.gov is based on storage volume. See https://cloud.gov/pricing/for more information.
The text was updated successfully, but these errors were encountered:
Description:
PostgreSQL major version 12 is being retired in February of 2025.
Actions
To avoid possible downtime and handle these database engine version upgrades during the most convenient time for your applications, please reply to cloud.gov support email to let them know which option we are selecting:
Heavily Recommended: Create a new db instance, migrate the data, test your application, delete the old db instance.
There is tooling provided at https://github.com/cloud-gov/cg-manage-rds which shows how to import and export brokered databases. Additional information for PostgreSQL version 15 can be found at https://www.postgresql.org/docs/15/release-15.html#id-1.11.6.13.4. Please note for PostgreSQL versions 15+ , using SSL is required when connecting to your database. As such, you will need to configure your client library to use SSL when connecting to your database.
Contact us and we will set the database instance to upgrade during the next maintenance window (Times are in UTC).
Contact us and we can schedule the upgrade during normal business hours.
Your database services that need to be upgraded are:
Org Space Instance name Engine Engine Version Maintenance Window (UTC)
gsa-18f-tock prod tockdb postgres 12.19 wed:11:06-wed:11:36
gsa-18f-tock staging tock-database postgres 12.19 sun:07:02-sun:07:32
The databases will be upgraded as per the upgrade path outlined in option #2, no earlier than February 10th, 2025 starting 12:00 AM (assuming you don’t choose to upgrade earlier) but please note that if a selection is not made by February 10th, your database engine version will be upgraded for you during the maintenance window.
There will be no increase in your Cloud.gov bill associated with these RDS PostgreSQL engine version upgrades. Currently, pricing for databases on Cloud.gov is based on storage volume. See https://cloud.gov/pricing/for more information.
The text was updated successfully, but these errors were encountered: