Key takeaways from the discussion
| Theme | What users said |
|---|---|
| Embedded columnar analytics boost productivity | “having an embedded column database for analytics in your traditional db is a massive win for productivity + operations simplicity.” – dzonga |
| Choosing a column‑store solution | “One option is TiDB. It has support for columnar data alongside row based data.” – travem “Can tiger data be used just as a simple column store?” – tempest_ “pg_duckdb seems pretty clean, due to Postgres’ powerful extension mechanisms.” – linuxhansl |
| Integration & compatibility concerns | “It is MySQL compatible, but not based on MySQL code so not quite what you asked for.” – travem “All I want is effectively what clickhouse does in PG. I have a single table that I need fast counts on and clickhouse can do the counts fast but I have to go through the entire sync/replication to do that.” – tempest_ |
These three points capture the main opinions: the value of columnar analytics inside a relational DB, the available options and their trade‑offs, and the practical issues of compatibility and data movement.