Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloud SQL for PostgreSQL now generally available

cloudplatform.googleblog.com

Post reply on HN
Print view View original

101–108 of 108 posts

Re: Cloud SQL for PostgreSQL now generally available

#101

Post by litewulf »

sirn wrote: post #89

Since there seems to be some Googler who work on Cloud SQL here, I wonder is there any chance Cloud SQL will be available in asia-southeast1 soon? It's the only region (I believe) where Cloud SQL isn't available at all, and one of the main reasons we can't fully migrated from AWS to GCP just yet.

[I am a Cloud SQL-er, and worked on region expansion... among other things]

Cloud SQL has only been available in regions with at least three zones (since we believe that is the minimum to make sure we can maintain HA in the event of a single zone failure). asia-southeast1 currently only has two zones, when a third zone is launched, Cloud SQL will become available in that region.

Re: Cloud SQL for PostgreSQL now generally available

#102

Post by litewulf »

foobarbazetc wrote: post #49

Do these use the standard persistent disks (capped at 240mb/s)?

[I am a Cloud SQL-er]

Yes, you can use both standard and SSD persistent disks. If you create a larger instance with more vCPUs and a big enough disk, you can achieve greater than 240mb/s, see the docs:

https://cloud.google.com/compute/docs/disks/performance#ssd-...

Re: Cloud SQL for PostgreSQL now generally available

#103

Post by optimusclimb »

litewulf wrote: post #75
optimusclimb wrote: post #59

Started down the path of using this when it was in beta, but had to abort when we saw there was no option to connect to it from Python App Engine Standard. Now that it's GA...it looks like that hasn't changed. Is the classic, Python, App Engine standard becoming a second class citizen? Or was there some reason why this wasn't considered GA worthy for Postgres? Trying to understand if going forward Google is trying to…

[I am a Googler and my team works on part of this] You can connect to postgres from app engine standard... as long as its Java. See this doc https://cloud.google.com/appengine/docs/standard/java/cloud-... And no, appengine standard is not a second class citizen. Hand-wave-ily, the connectivity path that flex uses works for postgres with minimal changes, but unfortunately some additional work is required to get appeng…

Thanks for that, but...not using Java.

Re: Cloud SQL for PostgreSQL now generally available

#104

Post by sirn »

litewulf wrote: post #101
sirn wrote: post #89

Since there seems to be some Googler who work on Cloud SQL here, I wonder is there any chance Cloud SQL will be available in asia-southeast1 soon? It's the only region (I believe) where Cloud SQL isn't available at all, and one of the main reasons we can't fully migrated from AWS to GCP just yet.

[I am a Cloud SQL-er, and worked on region expansion... among other things] Cloud SQL has only been available in regions with at least three zones (since we believe that is the minimum to make sure we can maintain HA in the event of a single zone failure). asia-southeast1 currently only has two zones, when a third zone is launched, Cloud SQL will become available in that region.

Thank you. That makes sense and totally understandable. Looking forward to when there's third zone in asia-southeast1. :-)

Re: Cloud SQL for PostgreSQL now generally available

#105

Post by ciguy »

tinix wrote: post #37
ciguy wrote: post #9

Earlier quoted context omitted.

Unfortunately last time I used CloudSQL for MySQL it was incredibly unstable. They would take down our master AND standby at the same time for maintenance. When we filed a ticket they just said it was a known bug with no plans to fix. A major client of mine migrated to AWS because of this and other issues.

I've been thinking about moving us to Google's Cloud Platform. What I found in regards to maintenance here: https://cloud.google.com/compute/docs/regions-zones/#mainten... states that they do live migrations without any down time. Can anyone elaborate? Is this only for Compute Engine? In that case, if one can run postgres on a Compute Engine instance, why not do that instead? Surely, if one can setup a highly availab…

Maintenance windows are set for the cluster, not single instances. We were distributed across 3 AZs and Google had no suggestions for mitigating the ~5 minutes of downtime we were seeing every week or two.

The whole experience was so amateur and unprofessional it really soured me on GCE. They do have some cool tech but it seems like their cloud division needs to mature a bit.

Re: Cloud SQL for PostgreSQL now generally available

#106

Post by gingerlime »

manigandham wrote: post #99
gingerlime wrote: post #81

Earlier quoted context omitted.

We’re using compose for redis, but we might switch it to aiven as well, despite aiven having some missing functionality... For Gcloud and especially in Europe, I think these two are the only options that I’m aware of (at least for PG and redis)

If you want managed Redis, there’s nothing better than RedisLabs

Yeah, I was practically begging them to offer service on GCloud in europe ... :) but they don't cover it...

Re: Cloud SQL for PostgreSQL now generally available

#107

Post by joatmon-snoo »

tacticus wrote: post #73
flamingcow wrote: post #50

Earlier quoted context omitted.

[I'm the Cloud SQL TL] No, it isn't. We agree with you that it's an important feature for managed databases, and we're working to get it right. We decoupled it from this launch to get PostgreSQL to GA faster.

Unrelated to pg but could you badger the spanner team to make a mini spanner product :) Related to postgres. We have many many concurrent connections but a load satisfied by an n1-standard-4 atm do you recommend a connection pooler or something to help us get down to the 100 to 200 connections we need to be at to use cloudsql?

A mini spanner product in what sense?

Re: Cloud SQL for PostgreSQL now generally available

#108

Post by bpicolo »

manigandham wrote: post #61
bpicolo wrote: post #57

Earlier quoted context omitted.

AWS and GCP both have nvme SSDs for instance types intended for big-ol DBs https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ssd-inst...

Yes, I know. This thread is about managed database services, specifically about Aiven vs cloud-direct. Aiven still runs VMs on AWS or GCP but offers nvme disks while neither RDS nor CloudSQL have that available.

Ah I see, i3 isn’t in the RDS pool yet. I imagine it will be eventually?
Post reply on HN