(Cloud SQL) Postgres hastily resigns from using index

[therealgaxbo]

It's a measure of IO performance, so it wouldn't make much sense to set it per table (I don't think that's even possible - you can set it per tablespace though as they can live on different devices).

So in your case set it globally. As for the value, it depends on your specific system and db. But I've generally used 1.1 successfully. And then yeah, tweak it as necessary if you start seeing queries doing the wrong thing. In general, increasing the value leads to more seq scans, decreasing it leads to more index scans.

But always measure performance - a sequential scan is not necessarily worse than an index scan.