... or if you had read the HN comments on that article: https://news.ycombinator.com/item?id=19768864 :-)
If they supported foreign keys, I’m pretty sure I’d have used it many times. It seems like a good way to efficiently represent multiple distinct types which have some shared columns and some non-shared columns.
I recently used table inheritance to great effect on a project, so I wouldn't write it off completely. My use-case was a bit different as it involved zero-downtime data imports from separate sources (concurrently), but it proved a great tool for the job.
I find how it's dismissed as a fad pretty humorous and actually a bit insightful.
>Table inheritance was a part of a fad wherein the database was closely coupled to object-oriented code. It turned out that coupling things that closely didn't actually produce the desired results.
If I'd read this first, I wouldn't have wasted Saturday finding out for myself why you shouldn't use it.