Cloud SQL for PostgreSQL now generally available

Post by manigandham » Wed, Apr 18, 2018, 9:22 PM UTC

gingerlime wrote: post #18

manigandham wrote: post #6

We actually just migrated off yesterday... we went with an independent vendor like Aiven instead of the clouds because they move too slowly and don't have enough features.

Like aiven or aiven? :) I’m not aware of too much competition in this space. We’re happy with aiven so far, but they’re quite unknown / under the radar it seems...

Post by contrahax » Wed, Apr 18, 2018, 9:34 PM UTC

zawerf wrote: post #13

How do you deal with custom extensions (for example plv8)? I started off with heroku and they don't support the same subset: https://cloud.google.com/sql/docs/postgres/extensions https://devcenter.heroku.com/articles/heroku-postgres-extens...

Post by kdv » Wed, Apr 18, 2018, 9:50 PM UTC

Post by kdv » Wed, Apr 18, 2018, 9:58 PM UTC

alexnewman wrote: post #26

kdv wrote: post #25

Does anyone have insight or experience using this in production? We're currently running PostgreSQL 10 w/ pg_partman on our own hardware but looking at a several options for cloud migration. Unfortunately, Citus Cloud on GCP doesn't appear to be an option (yet?) - Google Cloud SQL (PostgreSQL) - Citus Cloud (AWS Only) - Citus (managed ourselves) on GCP

citus isn't simply postgresql. It has many tradeoffs

Post by aserafini » Wed, Apr 18, 2018, 10:09 PM UTC

contrahax wrote: post #23

zawerf wrote: post #13

How do you deal with custom extensions (for example plv8)? I started off with heroku and they don't support the same subset: https://cloud.google.com/sql/docs/postgres/extensions https://devcenter.heroku.com/articles/heroku-postgres-extens...

They don't have a great story around extensions - the ones they do have are unsupported/buggy. For example, PostGIS is missing "ST_FromGeoJSON" because it was compiled with the wrong flag - and has been this way for over a year despite hundreds of user complaints.