Unable to migrate from CloudSQL Postgres to AlloyDB due to the google_vacuum_mgmt extension

Google Cloud Database
, ,
1

Hi there,

I’m trying to migrate data from a CloudSQL Postgres 14 into AlloyDB. Testing the migration fails with this error:

The extensions installed on the source database are either not supported or having unsupported versions.
database postgres has unsupported extensions installed: google_vacuum_mgmt; database other_db has unsupported extensions installed: google_vacuum_mgmt

I’ve checked and indeed, that extension is installed. However, since I don’t have a superuser, I can’t delete it. I haven’t found any flags to remove it either.

I looked at the logs and found this relevant bit:

{
  "textPayload": "2024-06-11 00:27:55.867 UTC [7]: [9-1] db=,user= LOG:  parameter \"cloudsql.enable_google_vacuum_mgmt\" changed to \"on\"",
  "insertId": "...",
  "resource": {
    "type": "cloudsql_database",
    "labels": {
      "project_id": "...",
      "database_id": "...",
      "region": "us-west1"
    }
  },
  "timestamp": "2024-06-11T00:27:55.867526Z",
  "severity": "INFO",
  "labels": {
    "INSTANCE_UID": "...",
    "LOG_BUCKET_NUM": "45",
    "SOURCE_ID": "..."
  },
  "logName": "projects/.../logs/cloudsql.googleapis.com%2Fpostgres.log",
  "receiveTimestamp": "2024-06-11T00:28:27.467459719Z"
}

but I couldn’t find a flag called cloudsql.enable_google_vacuum_mgmt

When I describe the instance, I see this:

geminiConfig:
  activeQueryEnabled: false
  entitled: true
  googleVacuumMgmtEnabled: true
  indexAdvisorEnabled: false
  oomSessionCancelEnabled: true

which hints to this being a Gemini in Databases related functionality. Even when calling the update endpoint, it’s clear that googleVacuumMgmtEnabled is not a field I can modify.

I tried ignoring the warning and proceeding with the migration, but I got the same error. I also tried disabling Gemini in Databases but it seems like it’s going to take 30 days.

Am I missing anything? Is it not possible to use the migrator for CloudSQL Postgres servers when Gemini in Databases is turned on? Is it possible to turn it off for a particular server? or turn it off in a way that enables us to migrate earlier than in 30 days?

Thanks!

4 Likes
2

We have the same problem. We need to delete the google_vacuum_mgmt schema ASAP, but we don’t know how to do it. Why does disabling Gemini in the Database need to take 30 days and not take effect immediately?

1 Like
3

We reached out to Google and they were able to disable Gemini in Databases for our project. After that, we were unblocked on the migration.

2 Likes