Hi Metabase team,
I’ve been a long time sufferer of this GitHub issue, which had gone away for the last couple of months. Unfortunately however, it came back roughly around the time I upgraded to 0.33.5. I don’t know for sure that 0.33.5 had anything to do with the error coming back or not, but the timing is suspicious.
My main question here is what should I do next to help get this resolved? The aforementioned ticket is already closed. Should I comment on that ticket, make a new ticket, etc…?
A couple of other notes: I’m on Elastic Beanstalk. Restarting my app servers seems to temporarily fix the issue for a short time, but then it comes back. I mainly see the error when Metabase is trying to sync. Here’s a stack trace snippet:
[5041e072-3c43-41e6-b682-aff4639922af] 2019-11-19T11:00:00-08:00 INFO metabase.sync.util STARTING: step 'sync-tables' for redshift Database 2 'Panoply'
[5041e072-3c43-41e6-b682-aff4639922af] 2019-11-19T11:00:00-08:00 ERROR metabase.sync.util Error running sync step: ERROR: type "e" does not exist
("org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440)"
"org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183)"
"org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308)"
"org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)"
"org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)"
"org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307)"
"org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293)"
"org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270)"
"org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:224)"
"org.postgresql.jdbc.PgDatabaseMetaData.getTables(PgDatabaseMetaData.java:1316)"
"com.mchange.v2.c3p0.impl.NewProxyDatabaseMetaData.getTables(NewProxyDatabaseMetaData.java:3010)"
"--> driver.sql_jdbc.sync$get_tables.invokeStatic(sync.clj:90)"