pg_clickhouse
Shares rank 11 of 14 Postgres extensions by recommenders
People recommend it as a Postgres extension that runs analytical queries and joins against ClickHouse while keeping OLTP queries in Postgres, with strong subquery pushdown.
People recommend it as a Postgres extension that runs analytical queries and joins against ClickHouse while keeping OLTP queries in Postgres, with strong subquery pushdown.
7 people gave an opinion
- recommend it
- 7
- criticize it
- 0
- approval share
- 100%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 7 people recommend itNeeds 10 or more, not met.
- Nobody criticizes itNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Pushes subqueries and joins to ClickHouse
“Correctly pushing subqueries while preserving the semantics of the original database is something I can't imagine I could've ever achieved”
Comment from 12 Aug 2026 in “pg_clickhouse v0.10: Subquery pushdown and 1000x faster TPC-H queries” “It lets you run OLTP and OLAP queries from Postgres, while pushing the analytical queries—and their joins—down to ClickHouse”
Comment from 14 Dec 2025 in “Pg_ClickHouse: A Postgres extension for querying ClickHouse” “Our main focus is comprehensive pushdown capabilities.”
Comment from 12 Dec 2025 in “Pg_ClickHouse: A Postgres extension for querying ClickHouse” Unified OLTP and OLAP query layer
“It lets you run OLTP and OLAP queries from Postgres, while pushing the analytical queries—and their joins—down to ClickHouse”
Comment from 14 Dec 2025 in “Pg_ClickHouse: A Postgres extension for querying ClickHouse” “since you'll be using a unified query layer for your application”
Comment from 12 Dec 2025 in “Pg_ClickHouse: A Postgres extension for querying ClickHouse”
Other Postgres extensions people recommend
The four most recommended other Postgres extensions, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 14 Postgres extensions, rankedWhat people said
11 of the 12 comments that mention it, newest first. Each links to the original comment.
“With pg_clickhouse this doubled throughput while reducing memory usage.”
“Correctly pushing subqueries while preserving the semantics of the original database is something I can't imagine I could've ever achieved”
“otherwise works pretty well”
“pg_clickhouse extension for querying CH from PG”
“It lets you run OLTP and OLAP queries from Postgres, while pushing the analytical queries—and their joins—down to ClickHouse”
“pg_clickhouse is a step in that direction”
“That would be incredible! So many times I want to reach for ClickHouse but whatever company I'm at has so much inertia built into PG.”
“since you'll be using a unified query layer for your application”
“Our main focus is comprehensive pushdown capabilities.”
“there are a lot of clickhouse fdw implementations and none of them are well maintained”
“This is pretty good. It will allow us to use PostgREST as an API endpoint to query the ClickHouse database directly”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.