supabase-js v2 abortSignal cancels the HTTP request, but does PostgREST stop the running Postgres statement?
Goal After migrating to supabase-js v2, I want to use the documented .abortSignal(signal) option on query builders (with AbortSignal.timeout(ms) ) to bound long-running PostgREST and RPC calls. The client-side behavior is clear: the pending promise rejects with a fetch-level AbortError. What I cannot determine is what happens on the server side once the HTTP
supabase