Closed steve-chavez closed 2 years ago
Partially addresses https://github.com/supabase/pg_net/issues/26. Memory leaks fixes will be different when https://github.com/supabase/pg_net/pull/50 is merged.
In theory we could grep the valgrind log file to setup a check in CI but this is not possible right now because there are traces unrelated to pg_net, as mentioned in https://github.com/supabase/pg_net/issues/26#issuecomment-947286896.
Partially addresses https://github.com/supabase/pg_net/issues/26. Memory leaks fixes will be different when https://github.com/supabase/pg_net/pull/50 is merged.
In theory we could grep the valgrind log file to setup a check in CI but this is not possible right now because there are traces unrelated to pg_net, as mentioned in https://github.com/supabase/pg_net/issues/26#issuecomment-947286896.