--- title: "v0.21.0: Fold Your SQL, Pick Your Page Size Per Tab, and Postgres Client Certificates That Actually Get Sent" url: https://daily.dev/posts/co05u7rpx source_url: https://tabularis.dev/blog/v0210-sql-folding-per-tab-page-size-postgres-mtls type: share source: "Lonely Programmer" author: "Andrea Debernardi" published: 2026-08-25T14:54:33.285Z updated: 2026-08-25T14:54:33.288Z tags: ["postgresql"] upvotes: 23 comments: 2 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # v0.21.0: Fold Your SQL, Pick Your Page Size Per Tab, and Postgres Client Certificates That Actually Get Sent **[Lonely Programmer](https://daily.dev/sources/lonely_programmer)** · [@andreadebernardi](https://daily.dev/andreadebernardi) · 23 upvotes · 2 comments ## Summary Tabularis v0.21.0 adds statement-level SQL folding with hover previews in the editor, a per-tab rows-per-page override for query results (including an All option to disable pagination), and PostgreSQL client-certificate (mTLS) authentication that was previously accepted in the UI but never actually sent to the server — fixing connections to servers like Google Cloud SQL that require client certs. Plugin installs can now be cancelled cleanly, the destructive-query and production-write safety guards are merged into one warning with an opt-in countdown, and the SSL-mode spelling migration introduced in v0.20.0 now also runs inside the standalone MCP process, closing a gap where connections opened only via MCP stayed on stale cleartext settings. A long tail of community fixes covers multi-statement exports, hidden SQLite virtual-table columns, database-qualified table editing, a manual TablePlus import path, and a Snap launcher entry. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 2 upvotes > Accepting client certificates in the UI while never sending them is exactly the kind of security bug that a real mTLS integration test should catch. It is also good to see the standalone MCP path included in the SSL-mode migration instead of assuming every connection shares one code path. **@agustinbarrientos** · 2 upvotes > An integration test should prove the mTLS client certificate reaches a real PostgreSQL server instead of merely surviving the settings form. ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments --- Tags: [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/co05u7rpx)