1
🚀 Architecture Proposal: `pg_agent` (In-Database Autonomous Agents via WAL Integration)
Source: supabase/supabase#43819 · opened by @allornothingai
🚀 Architecture Proposal: pg_agent (In-Database Autonomous Agents via WAL Integration) Hi Supabase Team, Supabase has democratized Postgres for the modern web, but the current paradigm for AI applications is fundamentally inefficient. Right now, to build an AI agent with Supabase, a developer must: 1. Listen to a webhook / Edge Function. 2. Pull data out of Postgres. 3. Send it to OpenAI/Anthropic. 4. Push the result back into Postgres. This creates latency, race conditions, and massive network overhead. I propose a groundbreaking architectural addition to the Supabase ecosystem: pg_agent - A native PostgreSQL extension for autonomous AI. The Vision: The Database IS the Agent Instead of externalizing the AI, we embed the autonomous logic directly into the database engine using the Write-Ahead Log (WAL) and native Postgres background workers. When a row is inserted (e.g., INSERT INTO support_tickets (issue) VALUES (...)), the pg_agent extension intercepts the event at the WAL le…
No pledges yet. Be the first to back this.
Comments
Similar requests
Include walg in supabase/postgres docker image?
2 votes · 0 comments
Publish "etl-core" as separate library on crates.io
1 vote · 0 comments
Add AgentScan to fight AI agent spam in your repository
5 votes · 0 comments
Proposal: document AgentsKit as a portable Supabase pgvector adapter for JavaScript agents
1 vote · 0 comments
Internationalization (i18n) Architecture for Supabase Studio
1 vote · 0 comments
No comments yet.