“ Select from 2 to 32 vCPUs; 8 GB - 64 GB RAM; 128 GB - 1 TB disk” how easy or fiddly is it for the end user to change specs? Are we responsible for migration?
Also, we can have as many databases as we want on our instance? Or just one?
Reiterating jpg’s question, does it have pgvector support?
What are your recommendations for connecting it to file store and/or blob store?
Do you have any support for backups?
Perhaps there is documention I missed, I read also the product and pricing pages.
Thank you! Quick notes:
- Resizing instances after provisioning is a manual operation for now. We'd use the same backup machinery that exists to automate it; until then you could do it manually or we're happy to help through a support request.
- Yes, you can create multiple databases per instance.
- We don't support pgvector yet; initial extensions we have are those in contrib, with more to come.
- Going through a VM to fetch the data from/send data to file store is the most common
- We take backups automatically, with point-in-time-recovery available to the minute. We also allow you to "fork" a database using a similar approach: i.e. your database remains intact; you just add a new database to it from a past point in time (typically useful for dev, test and/or analytics)
Some questions:
“ Select from 2 to 32 vCPUs; 8 GB - 64 GB RAM; 128 GB - 1 TB disk” how easy or fiddly is it for the end user to change specs? Are we responsible for migration?
Also, we can have as many databases as we want on our instance? Or just one?
Reiterating jpg’s question, does it have pgvector support?
What are your recommendations for connecting it to file store and/or blob store?
Do you have any support for backups?
Perhaps there is documention I missed, I read also the product and pricing pages.