Supabase client retry behavior and PostgreSQL upsert interaction for idempotent writes
Goal: Ensure that a write operation retried by the Supabase client does not result in duplicate rows in the underlying PostgreSQL table. The Supabase JavaScript SDK automatically retries failed network requests with exponential back‑off, but it does not deduplicate the corresponding INSERT or UPDATE statements. Developers must therefore rely on database‑leve