Skip to content

Google Cloud SQL / PostgreSQL

Info

Postgres 15 has changed the security model around the public schema and it is no longer world writeable. If you and your team make use of the public schema for interactive sessions and experimentation you will have to create separate schemas for separate users and share these role or user grants. Normal app usage will function normally.

PostgreSQL is a relational database which is a good choice for storing data that is relational in nature. In the nais platform, we use CloudSQL from the Google Cloud Platform to provide managed PostgreSQL databases.

Minimal configuration needed to provision a database for your application:

app.yaml
...
apiVersion: nais.io/v1alpha1
kind: Application
metadata:
  name: myapp
...
spec:
  ...
  gcp:
    sqlInstances:
      - type: POSTGRES_16
        tier: db-f1-micro
        databases:
          - name: mydb

The default configuration sets up the instance with:

  • 10 GB of SSD storage
  • no automatic storage increase
  • no high availability

See all configuration options in the application manifest reference.

Choosing the right tier for production

The minimal configuration above uses the tier db-f1-micro, which has 1 shared vCPU and 614 MB RAM. Tiers using shared CPUs (db-f1-micro and db-g1-small) are NOT covered by the Cloud SQL SLA and should not be used for critical production workloads.

Consider changing the tier to the db-custom-CPU-RAM tier for your production databases.

Please also note that exhausting disk and/or CPU with automatic increase disabled is not covered by the SLA.

How it works

The first time you deploy your application with the above configuration, Nais will provision the database into your team's own project in GCP. Your team has full access to view logs, create and restore backups and other administrative database tasks.

Nais also configures your application with the necessary environment variables needed to connect to the database. See the reference for the list of environment variables.

First time provisioning of the database will take some minutes. Your application may not be able to connect to the database until the provisioning is complete.

FAQ

FATAL: password authentication failed for user "<user>"

Answer

The synchronization of the password to the database may have failed. See workaround for password synchronization issues.

Cloud Sql Conditions messages

Invalid request: backup retention should be >= transaction log retention

Answer

This error occurs when the backup retention is set to a value lower than the transaction log retention. The backup retention should be equal to or greater than the transaction log retention. You can fix this by setting the retainedBackups to a value equal to or greater than the transaction log retention or by setting the transactionLogRetentionDays to a value equal to or less than the backup retention. This can be configured in the NAis manifest. Read more about automated backups with cloud sql.

Cannot disable cloudsql.logical_decoding while there are logical replication slots

Answer

This error occurs when you try to disable logical decoding while there are logical replication slots. Notes and limitations on disabling logical decoding.

...immutable field(s): [Field Name: settings.0.diskSize, Got: x, Wanted: xx]...

Answer

This error occurs when you try to change the disk size of the database instance. The disk size settings of the database instance cannot be less then current size after the instance is created. You can fix this by specifying in the Nais manifest the desired disk size of the database instance to be equal to or greater than the current size. If you want to control the disk size of the instance you should disable automatic storage increase.

Not allowed to do major version upgrade from POSTGRES_x to POSTGRES_xx

Answer

This error occurs when you try to 'upgrade' the major version of the database instance to a version that is not allowed. You cant downgrade the major version of the database instance, if you want to downgrade the version you need to create a new instance with the desired version. You can fix this by specifying in the Nais manifest the version type to the same as the current or a higher version.