TheOtherBrian1

It's been quite a while, is this issue still open?

Yeah, I can add it. I can work on creating a tutorials/examples section

In [Issue 62](https://github.com/supabase/pg_net/issues/62), you mentioned the following: > An alternative [to error recovery] could be logging the failed http requests. Then the user would have to search the pg logs....

> Hm, do you have examples of extension-related errors? I haven't experienced any yet, but I've thought about the potential for them to happen.

@shawnmclean, I've been thinking about rewriting the pg_net retry section. I have an [early draft](https://gist.github.com/TheOtherBrian1/0c8271feb1f4cb9d4468e605b4ec6334). I'm fairly confident in stages 1-6 and 8. It can be used as a basis...

@vickkhera I wasn't actually aware of the cause of the bug - I was only aware of how to reproduce it - but you seem to have noticed that the...

@waylon999 You can set the timeout to greater than 5000ms. That's a limitation imposed by the UI. You can write the webhooks directly in pg_net or use the [supabase_functions.http_request](https://supabase.com/docs/guides/database/webhooks) helper...

Hello, @vickkhera, By default, whenever the extension runs, it automatically deletes all rows that were created 6 or more hours ago. This design was specifically tailored for Supabase's webhook feature,...

@vickkhera, please consider the following advice with a grain of salt. While I have contributed to the extension by writing most of the documentation and fixing a few bugs, I...

@vickkhera In regards to your original problem about relaxed documentation, I decided to do another deep dive into the extension code and found the following function call in [worker.c](https://github.com/supabase/pg_net/blob/8b55e96d0d4b194dd8896b6f2a0fa8ef525aa8b3/src/worker.c#L448): ```...