[alyandon]

  PostgreSQL famously does not support plan hints 

I really wish the PostgreSQL core team would acknowledge that their stance on that hurts more than helps. Even Oracle with decades of engineering behind it doesn't get execution plans correct 100% of the time and provides a way to tune query execution via hints.

However, TIL that https://github.com/ossc-db/pg_hint_plan exists so that will probably become a standard thing I deploy.

[Shorel]

Famously, they didn't support Windows for the first decade of their existence, and that did cost them a tremendous amount of market share against MySQL.

By their technical merits, PostgreSQL should be the most used DB.

[alyandon]

I've followed the project since the 6.x days and I am still impressed that they managed (with the help of some really sharp win32 people) to get their fork-per-client model working on Windows.

[johnthescott]

yep. the windoze process model very much not like the unix process model. pg has been happily unix since 6.x days.

also, certain key players in pg community have threatened to quit if pg went the threaded execution model. getting threading correct is very, very difficult.

took many years (with much help from win experts) to get the port correct AND maintain the unix process-per-query model on unix.

[johnthescott]

i prefer the pg stance on no query hints. you can always install the extension.