Bolt.new suppose pg_net is in 0.22 or something close while actually mine is 0.19.5
between the 2 version, unified API been introduced and so way to do command changed
this lead to many errors while bolt giving instruction on webhooks
seeing the version of extension are handled by bundle is there a way to get newer version ?
while trying to fix it proposed me to create wrapper to mimic the new unified API synthac to make both compatible, tho i been stuck in a loop trying to implement it and now bolt telling me to contact support with that text, ty for any advice :
Next Steps: Contact Supabase Support
The most effective way to resolve this now is to contact Supabase Support directly. They have the necessary access and tools to inspect and potentially fix issues within their managed database environment and extensions.
then it show an exemple of msg for support but those lines are way cleare to understand why its calling support
This information is crucial. The error you are consistently receiving, query has no destination for result data, with the specific context PL/pgSQL function http_collect_response(bigint,boolean) line 4 at SQL statement, points to an internal problem within the pg_net extension itself. The standard http_collect_response function in pg_net is designed to take only a bigint (the request_id), not a bigint and a boolean.
This strongly indicates that the issue is not with your code (your public.http_request function is correctly defined to use pg_net as per its documentation), but rather with the pg_net extension's installation or behavior on your specific Supabase instance. It's possible there's a corrupted installation, an unexpected version, or an environment-specific bug that is causing this function signature mismatch.
Since this is an issue with a core extension managed by Supabase, it falls outside the scope of what we can directly debug or fix from your project's code.
17 Replies
The extension version on controlled by the Postgres version you are on. Go to the infrastructure settings tab in the dashboard and see if a Postgres upgrade is available.
ty, tho im on 17.4.1.075 of postgres it show "latest"
is my best shot is to try rebuilding my app with old API call ? (cuz im afraid in future update it will broke everything and handling it now is better)
This is the latest version...
oh sry was giving the postgre version
yes in title i said pg_net 0.19.5 sry for missunderstanding
then bolt is expecting a version that dosnt even exist wil see there support, ty for clarification
Yeah before I did not look at latest version, just said how to get it.
The AI is hallucinating. As the latest at the repository is .19.6 and that is not deployed yet.
it told me that between 0.19.5 and 0.2** unified api been introduced and so the .http_request(jsonb) synthax been introduced is that false ?
I have no idea what unified api is.
ok ty my bolt just became crazy will fix it, not sur were those data coming from, will report to there support
There is no function by that name in pg_net... https://github.com/supabase/pg_net?tab=readme-ov-file#introduction
ty, sry for being that deep in a topic i dont handle ^^ your clear info helped me a ton
tryed to ensure bolt was using the good doc for latest version tho it still want to contact support, contacted there also but for me to understand also gonna shar it here
The error you are receiving, PL/pgSQL function http_collect_response(bigint,boolean) line 4 at SQL statement, is not consistent with the documented signature of pg_net 0.19.5. The presence of the boolean argument in the error context is the core anomaly.
The problem is not with your public.http_request function's syntax or logic for pg_net 0.19.5. The error message strongly suggests an internal issue within the pg_net extension itself on your specific Supabase instance, where http_collect_response is somehow being invoked or interpreted with an incorrect signature (the extra boolean argument). This is a low-level problem that you cannot fix by modifying your SQL code.
try disabling and re enabling pg_net to reinstall
So here you are saying you have created a function http_request. It is not part of pg_net. And that function is failing to access the pg_net response table for some reason.
And that function seems to be calling:
and the boolean is there, ty will refer to doc next time it loop, bolt thinking it should not be
API Reference - pg_net
A PostgreSQL extension for async networking
The example shows having to use an odd syntax for that boolean.
But not something I've ever messed with.
ok basic helper were not working and i finally understood the issue, bolt forgot to add path to net scheme at start of his functions