Postgres and MySQL on Google Cloud

DBGorilla now supports Google Cloud, including Cloud SQL for PostgreSQL, Cloud SQL for MySQL, AlloyDB, and self-managed Postgres or MySQL on Compute Engine.

We started on AWS. Since then, teams running on Google Cloud have been asking when we would support their databases. That support is available today.

How it connects

You run a collector inside your Google Cloud project. It gathers information about your databases and sends it to DBGorilla over an outbound connection. There are no inbound firewall rules to open, and DBGorilla has no direct network access to your database.

The collector gathers schema information, index usage, query patterns, and resource allocation, tracking how they change over time. Query text leaves with the literal values already normalized out. Row content stays in your database, and customer data is never sent to a model.

Guidance for the database you run

Managed services give you control over some settings and handle others themselves. Advice to change an unavailable parameter is no use to the team responsible for the database.

DBGorilla’s guidance accounts for those limits, whether you use Cloud SQL, AlloyDB, or manage Postgres or MySQL yourself on Compute Engine.

Getting started

Our Google Cloud SQL and AlloyDB installation guide walks through setting up a collector on Compute Engine for Cloud SQL for PostgreSQL, Cloud SQL for MySQL, and AlloyDB.