restore message . . . cascade - Mailing list pgsql-admin

From Marc Fromm
Subject restore message . . . cascade
Date
Msg-id 81FEAB8CDDC62B42B6E8AA258228BC8804F108CC@EVS2.univ.dir.wwu.edu
Whole thread Raw
List pgsql-admin
I am backing up my databases with pgdump -c command to prevent duplicate
records during a restore.

When I restore the database with this command:
    psql -U postgres infoserv < /tmp/infoserv-03-25-2008_12-10
I get the message to use cascade to drop dependent objects.

DROP TABLE
ERROR:  cannot drop schema public because other objects depend on it
HINT:  Use DROP ... CASCADE to drop the dependent objects too.
ERROR:  schema "public" already exists
ALTER SCHEMA

1.) If the schema is not dropped during the restore, is stuff in the
schema being duplicated?
2.) What flag can I add to the pgdump command to initiate the cascade?
3.) Is it best practice to drop the schema and dependant objects?


Thanks,


Marc


pgsql-admin by date:

Previous
From: "Tena Sakai"
Date:
Subject: Re: it refuses to go down...
Next
From: kevin kempter
Date:
Subject: Deferred Constraints Issues