supabase/supavisor

Subscribe to tenant database write ahead logs

Open

#90 opened on May 16, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (2,191 stars) (106 forks)batch import
enhancementhelp wanted

Description

  • 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

Contributor guide

Tech stack
elixirpostgresql
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
PostgreSQL logical replicationElixir/Erlang OTP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
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