After upgrading windmill, we are now seeing this error "string too long to represent as jsonb string
This is a new error after upgrading. Although we were many versions behind, there weren't any breaking changes listed. Some of the job which used to run successfully, now run into this error "string too long to represent as jsonb string". I am pretty sure this is a Postgres issue but unsure why it now starting showing up. Any guidance would be appreciated
6 Replies
that looks like a postgres issue unrelated to the upgrade
GitHub
postgres/src/backend/utils/adt/jsonb.c at master · postgres/postgres
Mirror of the official PostgreSQL GIT repository. Note that this is just a mirror - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/...
how big is the result of your job ?
255MB is a lot for a single string
Thanks @rubenf . These flows generate very large spreadsheets and we've tried incrementally writting them into S3 but one of the jobs must be including all of the data as part of the response.
there is probably a way to do everything properly with s3 but can't help without more details
but yeah I think it's unrelated to the upgrade
Thanks for verifying. I didn't think it was but instead just it just coincided with the scaling problem we have with this data set.