<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clickhouse on Kuldeep Pisda</title><link>https://kdpisda.in/tag/clickhouse/</link><description>Recent content in Clickhouse on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/clickhouse/index.xml" rel="self" type="application/rss+xml"/><item><title>WalShadow Skips Logical Decoding. It Still Needs wal_level = logical</title><link>https://kdpisda.in/walshadow-postgres-wal-level-logical-still-required/</link><pubDate>Mon, 21 Sep 2026 09:00:00 +0530</pubDate><guid>https://kdpisda.in/walshadow-postgres-wal-level-logical-still-required/</guid><description>&lt;p&gt;On September 10, ClickHouse open-sourced WalShadow, a Postgres-to-ClickHouse replication engine that reads Postgres&amp;rsquo;s physical WAL instead of using logical replication. In ClickHouse&amp;rsquo;s own benchmark, a transaction committed in Postgres became visible in ClickHouse in about 200ms and the pipeline sustained 289,000 rows per second, against roughly 10 seconds and 120,000 rows per second for PeerDB, the logical-replication-based CDC tool ClickHouse acquired and already runs in production as ClickPipes.[1] The pitch is that going around logical replication removes its operational overhead: no replication slot, no output plugin, less load on the source.&lt;/p&gt;</description></item></channel></rss>