@Tim I hope you see this to fix/add an extra missing step to the pgcrypto extention creation in the domcumentation so no user will face the warning message Jeff posted if the user chose to create the extention on the dspace database instead of adding it to a schema.
Executing psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;" alone won't work unless the search_path is set to include the pgcrypto extention in it.
# This should work
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
2) psql --username=postgres dspace -c 'ALTER ROLE dspace IN DATABASE dspace SET search_path = "$user",public,extensions,pgcrypto;'
3) psql --username=postgres dspace -c 'SHOW search_path;'
# Or this one
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
2) psql --username=postgres dspace -c 'ALTER DATABASE dspace SET search_path = "$user",public,extensions,pgcrypto;'
3) psql --username=postgres dspace -c 'SHOW search_path;'
# Or this one if the search path is set globally in the main postgresql configuration file.
1) vi /path-to/postgresql.conf
search_path = '$user",public,extensions,pgcrypto'
# Or this one if the dspace script/scripts sets the search_path in them (SET search_path = "$user",public,extensions,pgcrypto;).
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
Trying to help.