You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ActiveRecord::StatementInvalid: PG::InvalidCatalogName: ERROR: database "postgres" does not exist
: SELECT t.oid, t.typname
FROM pg_type as t
WHERE t.typname IN ('int2', 'int4', 'int8', 'oid', 'float4', 'float8', 'bool')
The text was updated successfully, but these errors were encountered:
As a workaround, you can create an empty database postgres. This allows the catalogue lookup to continue. If you have a secure cluster, make sure that your rails user can access the postgres db.
I was stuck on this for awhile, not knowing how to even do the workaround, which was made a bit more complicated due to using docker, and not being able to get a cockroachdb binary to run in my alpine rails container. Eventually I went with a workaround in which I added the docker client binary to the image, mounted the docker.sock as a volume, and put this early in my application startup, before any rake db:* commands are executed:
The text was updated successfully, but these errors were encountered: