Hey gang, I have a (hopefully small) question: I have Dagster on EKS, and made an RDS instance for it to connect to.

dagster-webserver

and

dagster-daemon

pods are able to authenticate I believe, but the pods fail with an insufficient privileges error like so:

(psycopg2.errors.InsufficientPrivilege) permission denied for schema public: 
CREATE TABLE secondary_indexes (
                     ^

[SQL:CREATE TABLE secondary_indexes (
	id BIGSERIAL NOT NULL,
	name VARCHAR(512),
	create_timestamp TIMESTAMP WITHOUT TIME ZONE DEFAULT CURRENT_TIMESTAMP,
	migration_completed TIMESTAMP WITHOUT TIME ZONE,
	PRIMARY KEY (id),
	UNIQUE (name)
)

Now, I gave the dagster user on Postgres ownership on the

dagster

database it's connected to , and I can create that darn

dagster.public.secondary_indexes

table myself when I log on to RDS as the dagster user. Does anyone know what's going on? Where is it trying to make this table?

Hi Neil - hen Dagster starts up for the first time it will check to see if the tables that it needs exists on the RDS instance - if it doesn't, it will create them. Is it just that one table that's missing in your RDS instance, or is it having trouble trying to create any tables?

Hey Daniel! It's a completely fresh RDS instance, so all I did from there is make a

dagster

database and user, and give the user ownership on the

dagster

database. I'm able to create the table with the same SQL myself if I connect manually to RDS, so I don't understand why dagster can't unless it's trying to make it in another database aside from the one I told it about

Did it create any other tables?

I think the latter, I don't see any other tables

If you're able to kubectl exec into either of the pods you mention - I think this would be enough to trigger the schema creation if that helps troubleshoot:

from dagster import DagsterInstance
DagsterInstance.get()

What dagster does is uses sqlalchemy to create the tables using the postgres user / credentials that you set in the Helm chart. Are you sure you're using the same postgres schema and db when running the commands locally that you have configured in the helm cahrt?

100%. There's no other user on this instance aside from the root one, and it wouldn't have permissions errors if it was that.

That would be here: https://github.com/dagster-io/dagster/blob/master/python_modules/libraries/dagster-postgres/dagster_postgres/utils.py#L36-L67

Sure, here's what I got:

global:
  postgresqlSecretName: "dagster-postgresql-rds-secret"
postgresql:
  enabled: false
  postgresqlHost: "<http://blahblahblah.rds.amazonaws.com|blahblahblah.rds.amazonaws.com>"
  postgresqlUsername: "dagster"
  postgresqlDatabase: "dagster"
generatePostgresqlPasswordSecret: false

that does look pretty standard yeah..

Oh my gosh, that last bit was it:

GRANT USAGE, CREATE *ON* SCHEMA *PUBLIC*

*TO* dagster;

phew!

Here I thought setting the database owner to dagster would have given it everything, but I forgot public already existed