Thanks for reaching out! I checked in with the engineering team that owns this feature & they asked if you could create a separate resource in Retool with the connection string for Retool Database. It would be helpful for troubleshooting if we could check whether the new resource has the same issue
No, for troubleshooting purposes, we're wondering if you could create a new Postgres resource on Retool using the connection string copy/pasted from your Retool Database resource. We're curious if you then do the same select * from my_table query against the Postgres resource, do you get the same error?
The team also warned that the added size could potentially be from JSON serializations, in which case, we'd recommend using pagination or filtering your data