On Wed, Jul 8, 2020, 14:20 Mike Jumper <[email protected]> wrote: > On Wed, Jul 8, 2020, 13:17 mamet007 <[email protected]> wrote: > >> Using a fresh copy of RDS on AWS. I initialized the schema few times >> already >> here is the output of my 2nd attempt. >> > > The script is not idempotent, and multiple initialization attempts will > not be fresh. What was the output of your *first* attempt? > > If only specific columns are not being created, in this case a column > which uses a custom type, perhaps the user you are using to apply the > schema lacks necessary permissions? >
Also, from your previous message: > psql:db_schema_tamplate_output.sql:27: ERROR: type "guacamole_connection_group_db" already exists > psql:db_schema_tamplate_output.sql:36: ERROR: type "guacamole_entity_db" already exists > ... > psql:db_schema_tamplate_output.sql:737: ERROR: role "guacadmin" already exists What is this "db_schema_tamplate_output.sql"? Where is this "guacamole_connection_group_db" coming from and why does it think "guacadmin" is a role? The provided schema scripts do not include types called "guacamole_connection_group_db" or "guacamole_entity_db" (they are "guacamole_connection_group_type" and "guacamole_entity_type"), and "guacadmin" is not a PostgreSQL user/role but a Guacamole user. To PostgreSQL, "guacadmin" would just be arbitrary string data in a table. It looks like the script you're using is not the schema that we've provided, but rather another script based on that schema which has been modified such that it is incorrect. - Mike
