Postgresql RDS not responding to Memory and CPU parameter changes

Questions and Answers Deployment
, ,
1

It appears that we are stuck at t3.micro no mater although we set up CPU to 2 and Memory to 4 GB (which should be at a t3.medium.

_postgres_db_prod will be updated in-place

~ resource “qovery_database” “ltgres_db_prod” {
~ cpu = 1000 → 2000
~ external_host = "-> (known after apply)
~ id = " → (known after apply)
~ internal_host = “zsql” → (known after apply)
~ login = “” → (known after apply)
~ memory = 1000 → 4000
name = “Postgresql DB”
~ password = “” → (known after apply)
~ port = 5432 → (known after apply)
# (7 unchanged attributes hidden)
}

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
Terraform will perform the actions described above.
Only ‘yes’ will be accepted to approve.

Enter a value: yes

: Modifying… [id=af01]

Modifications complete after 1m12s d]
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

2

Update, it appears that changes is queued up, but I am unable to apply it. It shows as pending modification. Restarting cluster from Qovery console did not help. How can I apply the change to take effect?

Also, it appears there is no maintenance plan on the db, is that something special we need to set, or will Qovery take care of that? Thanks!!!

3

Yes, changes are not immediate, because at the moment it applies only during the maintenance window (Tue:02:00-Tue:04:00). Not very convenient for your use case.

This is something we definitively should update with “apply immediately” instead (current values engine/common-variables.j2.tf at main · Qovery/engine · GitHub).

The minor upgrade is set by defaults, so you don’t have to care about it, however, major upgrades are on your side. You decide when you want to upgrade databases (generally because it’s strongly linked to the applications using the database as well)