p:: PostgreSQL f:: pg_dump
# pg_restore -c -U <username> -h <host> -p <port> -d <db_name> <dump_file_name>
pg_restore --verbose --clean --no-acl --no-owner -h localhost -U prisma -d prisma customdumpfile
man pg_restore
...
-c
--clean
Clean (drop) database objects before recreating them. (Unless --if-exists is used, this might generate some harmless error messages, if any objects were not present in the destination database.)
--no-acl
Prevent restoration of access privileges (grant/revoke commands).
-O
--no-owner
Do not output commands to set ownership of objects to match the original database. By default, pg_restore issues ALTER OWNER or SET SESSION AUTHORIZATION statements to set ownership of created schema elements. These statements will fail unless the
initial connection to the database is made by a superuser (or the same user that owns all of the objects in the script). With -O, any user name can be used for the initial connection, and this user will own all the created objects.
...