This message was deleted.

We fixed this bug last week in https://github.com/growthbook/growthbook/pull/1184

excellent, didn’t see that in my quick scan. I will update our build.

We had been testing queries on Postgres, assuming Redshift would behave similarly. We've since added Redshift to our testing infrastructure, so hopefully we can catch these types of errors before they go live in the future.

yup, makes sense, much of the time postgres is sufficient.