Can you describe a use case where postgres performs badly, or why you prefer XYZ ? In my experience, on commercial projects, using 9.4+ postgres GIN tag/keywor

Can you describe a use case where postgres performs badly, or why you prefer XYZ ? In my experience, on commercial projects, using 9.4+ postgres GIN tag/keyword search index is very fast over data on the order of 30 to 100 million records, providing you have a host with SSD disks. I call this size data "MID" data, not "BIG" data, and it seems applicable to a lot of startups before they get to a million customers, and for a lot of real world customer data use cases. Also, a lot of startups need to handle gps geo-coordinates .. having used them, I have to say that the primitives that come with postGIS are pretty superb, and easily integrated. Outside startup-land, there are a lot of companies using horrible data systems, dying to get to their data quickly, who could be much better served with postgres via a web front end. ( Lowering the cost/time to build that is something I'm working on ) So if : * you want fast tag search * your data has locations or nearby-x * you'll have < 1bn rows for some time * your data is worth money then imo, postgres+postGIS+GIN+SSD is pretty compelling. That covers a lot of startup and business surface area.