supabase/supavisor

Subscribe to tenant database write ahead logs

Open

#90 创建于 2023年5月16日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Elixir (2,191 star) (106 fork)batch import
enhancementhelp wanted

描述

  • Postgrex.ReplicationConnection behavior
  • Configurable: should be able to setup the replication connection however a tenant would want
  • Verify configuration on connection and error if tenant publication does not match expected configuration

Why?

  • Trigger hooks from matching records somehow
  • Bust any query caches based off of the write ahead log

贡献者指南

技术栈
elixirpostgresql
领域
backenddatabase
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
PostgreSQL logical replicationElixir/Erlang OTP
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
First, review the Postgrex.ReplicationConnection documentation to understand the callback module structure. Then, design a GenServer that handles the replication connection, allowing configuration of the slot and publication names. The issue also suggests verifying the publication matches expected configuration on connect. Finally, consider how to expose events to trigger hooks and invalidate caches.
Subscribe to tenant database write ahead logs · supabase/supavisor#90 | Good First Issue