Create Vectors with Self Hosted

💬 Self Hosted Retool
1

I am trying to create Vectors on a Self Hosted deployed on GCP, using Kubernetes. I am using Retool version 3.196.8. I already enabled Retool AI with Retool Managed OpenAI and I've already created the extension pgvector on the Retool Database. However, when I try to create the Vector, I am getting the message below:

You must have Retool Database enabled to use Retool Vectors

note: I have followed this one to configure vectors on postgres: Enable Retool-managed Vectors on self-hosted deployments | Retool Docs

2

It looks like you’ve already taken most of the right steps, enabling Retool AI, using the Retool-managed OpenAI, and installing the pgvector extension. However, the error message "You must have Retool Database enabled to use Retool Vectors" suggests that the issue is with the Retool Database itself not being properly enabled or recognized. Even though you created the extension, make sure that you're actually using the Retool-hosted database and not just a custom Postgres instance.

3

Check that you've enable vectors on the correct database. There are 2, one for the retool installation and one (or more) databases for the Retool Database functionality (the one you access from Retool)

4

Hi Guys,

Thanks! Yeah, I've created the pgvector extension on the Retool Database functionality. However, how can I configure Vectors to use this database? I couldn't find anything related to this here:

Thanks!

5

Then it should just work when you add documents as vector in the resources screen.

1 Like
6

Hi @Marcus_Santos,

Just wanted to check in to see if @mbruijnpff's suggestion was helpful and if you needed any additional set up steps or if it now works when you add documents as vectors from the resources page!

7

Hi @Marcus_Santos any updates on if this is working as intended now? Or if you had any other steps needed to get things working?

9

Hi @Jack_T , at the end, I decided to recreate the Resources database and, then, I started to work properly. I don't why exactly it did not work before that. :grinning:

1 Like
11

Hi @Marcus_Santos,

That is great to hear! Happy it was resolved. It sounds like the resource/database had gotten into a corrupted state and just needed a hard refresh to get everything working as expected :raised_hands:

1 Like