Re:Lessons learned scaling a PostgreSQL database to 1.2bn re...
by thockingoog on Tuesday January 29, 2019 @10:16PM
(#19032322)
LOL. Thanks for the shout out. I am sorry you had a bad experience. Please be assured that we are working on it, and that we take this seriously.
Re:Lessons learned scaling a PostgreSQL database to 1.2bn re...
by honkycat on Thursday January 31, 2019 @06:31PM
(#19050118)
If I may be so bold, where should I direct this complaint so that people hear it:
When you delete a CloudSQL instance, it also deletes the back-ups associated with that instance along with it.
There is also no way to mark a CloudSQL instance as "protected" so one bad keypress can lose you your production database and all backups.
This is... cartoonishly dumb. Clownish.
- Cloudsql instance deletion protection should exist
- Those backups should be preserved somewhere when I delete the instance.
Re:Lessons learned scaling a PostgreSQL database to 1.2bn re...
by sandGorgon on Friday February 01, 2019 @12:30AM
(#19051890)
agreed - backups have nothing to do with an instance. i should be able to spin up and down postgresql instances, but backups should be stored (and billed) as per cloud storage rates.
Re:Lessons learned scaling a PostgreSQL database to 1.2bn re...
by dstroot on Tuesday January 29, 2019 @03:44PM
(#19029646)
Tim Hockin is my freakin hero.
Re:Lessons learned scaling a PostgreSQL database to 1.2bn re...
by sandGorgon on Tuesday January 29, 2019 @12:47PM
(#19028274)
There's a Google cloud slack channel?
Can you link ?
We had a production Kubernetes outage caused by a bug in Google Cloud. We were paying for gold level support.
They deescalated and reescelated our ticket 3 times.
In the end they closed the ticket and sent me a link to "Architecting distributed application" docs. I think they were trying to be condescending. That idiot should have been canned.
Eventually I threw a big fit in the Google Cloud slack channel and thockin ended up looking at the issue and finding the bug.