time_bucket does not exist
TimeScaleDB is enabled in extensions, but when I try to use
time_bucket
I get Failed to run sql query: function time_bucket(unknown, timestamp with time zone) does not exist
, any ideas?
https://docs.timescale.com/api/latest/hyperfunctions/time_bucket14 Replies
Do you have extensions in the search_path?
It could also be a parameter miss match in your call, but I don't know that extension.
I'm using the sql editor in the webapp, the cron extension and http extensions work fine, but none of the timescaledb functions show up in the intellisense
it's definitely installed

maybe it's cause the timescaldb schema is
graphql_public
, but I tried OPERATOR(graphql_public.time_bucket)
and that didn't work eitherI don't know much about it, but seems odd for that to be in graphql_public
Oh I figured it out
alter user supabase_admin set search_path = public,extensions,graphql_public;
and now it worksSo I just installed it, and there is a field to fill in when installing about the extension it goes in.
ah, my colleague must have not filled that out 😆
the schema it goes in.
You might want to uninstall and reinstall. Not sure you want it in graphql as that is used for .... graphql.
great, thanks so much for your help :supafire:
now I can't uninstall it 😅

yikes. let me see if I can uninstall it....
uninstalled and cleaned up dozens (hundred?) functions it had created.
When you look in the extension screen did it actually say it was in graphql_public? Was not clear how you got that. Mine said it was in extensions when I went to delete it.
I've only seen about a dozen users talking about using it here and github, so not sure how much help there is.
If this is an instance with alot of stuff on it, you may need to contact support.
If this is an instance with alot of stuff on it, you may need to contact support.
my colleague enabled it, he said he put graphql by accident

I just toggled that green button and it was gone.
But I also did not run anything with it.
It is possible if you ran anything, there is some cleanup that has to be done first.
It is also possible there is a grant issue with using that schema.
I would not think something else in the schema would hurt it, as extensions schema has many extensions in it.