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

61–70 of 108 posts

Re: Cloud SQL for PostgreSQL now generally available

#61

Post by manigandham »

bpicolo wrote: post #57
manigandham wrote: post #54

Earlier quoted context omitted.

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

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.

Re: Cloud SQL for PostgreSQL now generally available

#62

Post by manigandham »

TurningCanadian wrote: post #58
aserafini wrote: post #29

Earlier quoted context omitted.

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.

They're all the same quality. Sometimes great, sometimes terrible, but will get the job done as long as you put in the effort. Also bigger customers will obviously get more.

GCP does win on pricing now with role-based support that is a flat rate per user: https://cloud.google.com/support/role-based/

Re: Cloud SQL for PostgreSQL now generally available

#63

Post by manigandham »

flamingcow wrote: post #52
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?

Major: Upgrade to latest version, 9.6 is 18 months old. Cross-region replication.

Minor: less downtime for maintenance, point-in-time restore

The rest is summed up here: https://news.ycombinator.com/item?id=16872723

Re: Cloud SQL for PostgreSQL now generally available

#64

Post by tarr11 »

theptip wrote: post #60
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.

From the docs:

https://cloud.google.com/sql/docs/postgres/connect-external-...

> You can grant any application access to a Cloud SQL instance by authorizing the IP addresses that the application uses to connect.

> You can not specify a private network (for example, 10.x.x.x) as an authorized network.

> PostgreSQL instances support only IPv4 addresses. They are automatically configured with a static IP address.

Re: Cloud SQL for PostgreSQL now generally available

#65

Post by brdd »

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

We've been running a production workload on Postgres/Google Cloud SQL for about half a year now.

While things are good for the most part, a couple of serious problems related to connectivity have us completely boggled. We're connecting from Google Kubernetes Engine, which seems like it should be a standard combination, but run into constant problems that we've dumped many many hours into debugging.

We still haven't figured this problem out. I've found the docs to be very weak on Google's part. A lot of the troubleshooting tips are not very helpful (and can consist of unhelpful broad strokes like "be sure to use indexes!"). Because Google Cloud is not as popular than AWS, there is less community guidance from others. And what guidance does exist is often in forum threads that feel less than reputable. There's a big push to try to get you to talk to sales rep that are not technically knowledgeable and just try to upsell.

Very frustrating. Unclear if moving back to AWS, or hosting our own Postgres, would help.

Re: Cloud SQL for PostgreSQL now generally available

#67

Post by sandGorgon »

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.

It's way more expensive. Have you found ROI there ?

Re: Cloud SQL for PostgreSQL now generally available

#68

Post by jerrysievert »

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

at the least, they were waiting for timeouts to appear in plv8, which came in at 2.3.1 - I do not know the current status of it being brought into cloud sql though.

Re: Cloud SQL for PostgreSQL now generally available

#69

Post by manigandham »

sandGorgon wrote: post #67
manigandham wrote: post #54

Earlier quoted context omitted.

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.

It's way more expensive. Have you found ROI there ?

For our needs, yes. They run on cloud VMs so there will be a markup but their startup-4 and higher plans on GCP use local NVME SSDs so we get much better performance for the price.

We also make use of cross-regional replicas and are looking at doing it across clouds so if you want that then there isn't any other option other than doing it yourself. It's more of the complexity of this deployment rather than raw db size for us so if you have several TBs then maybe it's not the best fit.

Re: Cloud SQL for PostgreSQL now generally available

#70

Post by sitkack »

Goopplesoft wrote: post #22
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...

https://cloud.google.com/sql/docs/postgres/extensions Looks like a preset list of extensions. I'd assume custom extensions would be very difficult to support in managed postgres.

Why is that?

Systems are built for extension, to not allow it deprives one of essential qualities.

Post reply on HN