`count: exact` and `head: true` hides errors

[steve-chavez]

Problem

If a table has a high count (say 30_000_000), doing:

supabase
.from('table')
.select('id', {count: 'exact', head: true})

Will result in an uninformative error:

{
error: { message: '' },
data: null,
count: null,
status: 500,
statusText: 'Internal Server Error'
}

By removing the head: true (untested, but assuming is the same as curl), we get the actual error:

{"code":"57014","details":null,"hint":null,"message":"canceling statement due to statement timeout"}

Solution

Somehow expose the error message when this happens. Not sure if possible, this might need a special status code from upstream.

[mandarini]

I will be closing this issue since it has no activity for more than 2 years. If you find that the issue persists in the latest version of the libraries, please feel free to open a new issue.

Thank you for your patience and for contributing to supabase!

[laurenceisla]

@steve-chavez I think this is solved by the Proxy Status Header, right? Just tried it in Supabase-JS and it returns proxy-status: PostgREST; error=57014 as a response header.