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

51–60 of 108 posts

Re: Cloud SQL for PostgreSQL now generally available

#51

Post by flamingcow »

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

[I'm the Cloud SQL TL] Note that we currently only support PostgreSQL 9.6. Obviously supporting major versions across both MySQL and PostgreSQL is a priority for us.

Re: Cloud SQL for PostgreSQL now generally available

#52

Post by flamingcow »

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.

[I'm the Cloud SQL TL] What features would've kept you on Cloud SQL?

Re: Cloud SQL for PostgreSQL now generally available

#53

Post by flamingcow »

daj40 wrote: post #14
lobster_johnson wrote: post #5

Has anyone used the beta and got any feeling for how maintenance downtime impacts things? A bit nervous about how you can only set a "maintenance window" and not be able to plan ahead for disruption; as far as I can tell, they won't even tell you ahead of time. The HA seems really solid (zero-lag "regional disks"), but it's still a bit disconcerting.

The updates take the entire instance down for 2-5 minutes each month. While you can't avoid them, they can be scheduled for particularly low traffic times. If you're trying to avoid downtime, its a giant PIA. Even with HA enabled, you still lose master, slave and read replicas. Not entirely sure what they define HA as, but a mandatory monthly downtime doesn't usually fit into mine. [Update] That said, from what I und…

[I'm the Cloud SQL TL] I can't comment on timelines, but we're aware that customers are interested in more features around maintenance window scheduling, deferral, and notification, as well as shorter downtime for updates and smarter scheduling within a group of replicas.

Re: Cloud SQL for PostgreSQL now generally available

#54

Post by manigandham »

misterbowfinger wrote: post #46
manigandham wrote: post #35

Earlier quoted context omitted.

We did, but now use https://aiven.io Highly recommended if you want a fast and featured managed db service.

what's the benefit of using them vs. AWS or GCP directly?

Latest software (using v10.3), better performance (nvme SSDs), better backups (point in time, instant cloning), better features (more extensions, cross-region replication even across different clouds), better flexibility (migrate master across different clouds), better monitoring (logs and datadog metrics export), and more focused support with a smaller team.

Re: Cloud SQL for PostgreSQL now generally available

#55

Post by gleenn »

flamingcow wrote: post #50
pritambarhate wrote: post #19

Is point in time recovery available now in GA? I had checked it a couple of weeks ago for the beta service and it was not available. I think for a managed DB hosting point in time recovery is a critical feature.

[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.

What's a TL?

Re: Cloud SQL for PostgreSQL now generally available

#56

Post by gauravphoenix »

gleenn wrote: post #55
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.

What's a TL?

tech lead?

Re: Cloud SQL for PostgreSQL now generally available

#57

Post by bpicolo »

manigandham wrote: post #54
misterbowfinger wrote: post #46

Earlier quoted context omitted.

what's the benefit of using them vs. AWS or GCP directly?

Latest software (using v10.3), better performance (nvme SSDs), better backups (point in time, instant cloning), better features (more extensions, cross-region replication even across different clouds), better flexibility (migrate master across different clouds), better monitoring (logs and datadog metrics export), and more focused support with a smaller team.

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...

Re: Cloud SQL for PostgreSQL now generally available

#58

Post by TurningCanadian »

aserafini wrote: post #29
contrahax wrote: post #23

Earlier quoted context omitted.

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.

This is what I expect from Google. They are not customer-centric and no-one is really prioritising or cares about customer feedback.

You clearly have never talked to GCP support. They're in a different league from AWS support.

Re: Cloud SQL for PostgreSQL now generally available

#59

Post by optimusclimb »

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 push everyone to the flexible environment or not - as I would have really expected connectivity between these two products.

Re: Cloud SQL for PostgreSQL now generally available

#60

Post by theptip »

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…

Last I checked it wasn't possible to whitelist internal IPs (e.g. Kubernetes nodes or VM instances) to access Cloud SQL instances at all -- the options are either to use the non-standard cloud SQL proxy sidecar app, or allow connections from all endpoints (public or private).

This seems like a major omission, and AWS has had this for ages.

Post reply on HN