News for hackers. Stuff that matters.

A comment on Lessons learned scaling a PostgreSQL database to 1.2bn records/month. Parent comment

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.

[ Parent | on HN ]
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.
[ Parent | on HN ]