1
Support For PUT in pg_net
Source: supabase/supabase#41135 · opened by @erichosick
The pg_net extension currently supports GET, POST, and DELETE methods. Adding PUT would enable idempotent write operations directly from PostgreSQL. For example, calling net.http_put('/resources/123', payload) multiple times yields the same result, making it well-suited for database triggers, cron jobs, and webhook integrations where network failures or transaction retries may cause duplicate invocations.
Like POST, PUT would operate as fire-and-forget, queuing the request in net.http_request_queue and returning a request_id for optional response tracking. The function signature would follow the existing pattern: net.http_put(url, body, params, headers, timeout_milliseconds).
Like POST, PUT would operate as fire-and-forget, queuing the request in net.http_request_queue and returning a request_id for optional response tracking. The function signature would follow the existing pattern: net.http_put(url, body, params, headers, timeout_milliseconds).
No pledges yet. Be the first to back this.
Comments
Similar requests
expand pg_net functionality with more operations and other data types?
1 vote · 0 comments
suggestion: output logging for pg_net errors
1 vote · 0 comments
pg_net: Add max_concurrency parameter (or include concurrent requests in the batch_size)
1 vote · 0 comments
Allow making multiple `pg_net` requests in parallel from a query
2 votes · 0 comments
PG_NET - Http request queue priority
1 vote · 0 comments
No comments yet.