rvs-ie

> For me personally, A bridge with a 99.9% chance of not collapsing in a given year is good enough.

So you are ok if in a city with 100 bridges there is an average of one collapse every 10 years?

Even banks use more energy than bitcoin (which I highly doubt and there are comments here suggesting it's nowhere close), you'd still need banks or analogues of even if the whole humanity suddenly moves to crypto.

Crypto energy consumption is just unnecessary waste.

Bad analogue.

When trains ran on coal there was pretty much no alternative. Also more economical trains generally were in preference.

There is alternative to crypto _today_ which does not require unreasonable amounts of energy. Cryptobros don't care just like they don't care that crypto energy consumption only seems to go up.

No, it's currently public IP only.

We know. That's why PostgreSQL pilots hopefully clearer pricing structure where you choose how much CPU and RAM is needed and pay per CPU and GiB of ram. No more `db-nX-<something>-X`.

You'll still see instance size names for a while though. I think D0-D32 are for first generation of CloudSQL (which is MySQL only). db-* are for second generation and match GCE instance names.

More extensions is something we definitely plan to do.

No timeline, partially because we don't know ourselves. Our main priority for next few weeks will be ensuring everything is nice and stable. Once we are confident in current feature set we will start adding more. You can watch https://cloud.google.com/sql/docs/postgres/release-notes for news.

Source: I work on Cloud Postgres.