One of the many papercuts was actually more serious, to the point it was funny: I remember how in their stable versions, they had a humorous bug: if you did \copy instead of insert to a timescaledb, the timestamps looked right when you eyeballed them with a select, but acted wrong when you used them in a query.
Theefore it passed tests, but took down production whenever than happened. Ouch.
To their credit, they preserved this bug very well for several stable versions - for far longer than my patience with broken software.
That's quite bad for a database that intends to do timeseries - something so basic you won't ever see in proprietary software.
Then before there was pipelinedb which also had its fair share of bugs before going under. Some of them took a production database offline. But it was such a CPU hog that it had been anticipated.
Still after that timescaledb bug, I banned the use of third party postgres extensions.