3

You can follow your original strategy with a minor tweak: add Google Compute (GC) nodes into the current replica set and keep them in sync until ready to cut over. The only thing you need to change is to set those new GC nodes to have priority 0. They will be full members of the set, they just cannot be elected primary (or trigger elections). Once you are ...


1

Do you really need compressed? A multi-terabyte datasets may happily live on 100G-RAM machine. What is your data like? Text? Blobs? Lots of rows? Care to share the CREATE TABLEs? I don't have any details on Cloud SQL. But... Compression is usually not the first place to look when thinking of Scaling. It has overhead (usually CPU, sometimes complexity). ...


1

Are your instances 1st or 2nd generation? The activation policy configuration for 1st generation instances can cause your instance to automatically shut itself off after 15 minutes of inactivity. Regarding your bottom-line question: yes, instances are set to automatically shutdown (both generations) for maintenance. For second generation instances, you can ...


1

To answer my own question, GCP (and AWS) snapshots are mostly consistent, but in a very write heavy database, you would want to lock the tables for the duration of the snapshot backup. I believe there is actually an system level option to lock the drive itself for the snapshot, but that is not necessary for my use-case. I ended up using both methods to ...


1

raster2pgsql This a helper to make the job easy. It's not strictly speaking required. raster2pgsql is a raster loader executable that loads GDAL supported raster formats into sql suitable for loading into a PostGIS raster table. It is capable of loading folders of raster files as well as creating overviews of rasters. You can just redirect the output ...


1

In GCP it'll be a two step process: You should be able to create Log Filters: https://cloud.google.com/logging/docs/view/advanced-filters And then use those log filters to create metrics: https://cloud.google.com/logging/docs/logs-based-metrics/counter-metrics This won't be as flexible or seamless as a SQL query, but the filters should provide you with ...


1

I have seen this happens a lot in Amazon RDS. This occurs with row-based replication when a Master get hammered with lots of writes and they get serialized to one I/O thread. What you should do is dynamically change the following: SET GLOBAL innodb_flush_log_at_trx_commit = 2; Problem is you need the SUPER privilege, which neither Amazon RDS nor Google ...


Only top voted, non community-wiki answers of a minimum length are eligible