Only in some cases of churn plus there are plenty of workarounds where you sacrifice some performance and/or usability to avoid the bloat so I would still recommend PostgreSQL since few databases consist only, or almost only, of the bad cases for bloat.

I used to work in online gambling where we had plenty of row churn and not much bloat at all without having to use any of the workarounds.