RetoolDB Limits

  1. My goal: I am using my RetoolDB in a Next.js app and managing the tables via Retool UI and workflows
  2. Issue: I noticed today after doing a bunch of bulk updates that I hit a RetoolDB limit
  3. Steps I've taken to troubleshoot: I looked here Retool Database usage and limits | Retool Docs but did not see any mention of limits.
  4. Additional info:

Here's what I see in the Retool Workflow console:

Here is what I see in my logs:

Database query error: error: remaining connection slots are reserved for non-replication superuser connections
    at async f (.next/server/chunks/ssr/[root-of-the-server]__8ab7d1a5._.js:1:10299)
    at async i (.next/server/chunks/ssr/[root-of-the-server]__efff5e4c._.js:1:10769) {
  length: 102,
  severity: 'ERROR',
  code: 'XX000',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: undefined,
  line: undefined,
  routine: undefined
}

Hey @Eriks_Reks - thanks for reaching out. You're right that we don't explicitly communicate a lot of the limitations associated with RetoolDB. We recently added the following blurb, but I'm happy to provide some more detail.

Retool Database is designed to be a convenient way to store data to use within or outside of Retool. It is not designed to be a highly-available, scalable database service, and you should use a separate managed database provider if your use case requires these guarantees.

In addition to the documented 5GB ceiling on overall storage space, we currently enforce the following:

  • Requests per minute: 1000
  • Dedicated compute: 0.25 vCPU and 1GB RAM
  • Connection count: 112

If you are connecting to the DB via the connection string we expose in the UI, I strongly recommend you use the variant that utilizes pooling! Let me know if you have any additional questions.

1 Like