<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Supabase on Kuldeep Pisda</title><link>https://kdpisda.in/tag/supabase/</link><description>Recent content in Supabase on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 24 Sep 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/supabase/index.xml" rel="self" type="application/rss+xml"/><item><title>Supabase Killed logs.all Yesterday. Its Own Migration Guide Names the Wrong Column</title><link>https://kdpisda.in/supabase-logs-endpoint-source-column-migration-bug/</link><pubDate>Thu, 24 Sep 2026 09:00:00 +0530</pubDate><guid>https://kdpisda.in/supabase-logs-endpoint-source-column-migration-bug/</guid><description>&lt;p&gt;On September 23, Supabase removed the &lt;code&gt;logs.all&lt;/code&gt; Management API endpoint and moved programmatic log querying to a new, ClickHouse-backed &lt;code&gt;logs&lt;/code&gt; endpoint.[1] Anyone with a script, log shipper, dashboard, or MCP-connected agent that calls &lt;code&gt;.../analytics/endpoints/logs.all&lt;/code&gt; directly had two months of warning and, as of yesterday, no fallback. The migration itself is a real architecture change, not just a renamed path. But the changelog Supabase wrote to walk people through it contains a wrong column name in its own example query, one that a user flagged in a bug report a month before the deadline and that never got corrected.&lt;/p&gt;</description></item></channel></rss>