Date: Wed, 31 Jul 2013 00:00:38 -0700 (PDT)
From: Samrat Revagade <revagade.samrat@gmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <1375254038816-5765716.post@n5.nabble.com>
In-Reply-To: <6E551FFA49836D4290CA09616AE1CB9BB14718@EX01.SPDFRAK.BLN>
References: <6E551FFA49836D4290CA09616AE1CB9BB14718@EX01.SPDFRAK.BLN>
Subject: Re: Restore after using pg_dumpall
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

>pg_dumpall > alldb.sql (store)
>and
>psql -f alldb.sql postgres (restore)
>is it necessary to drop existing objects (for example roles, ...) ?
>Any help is appreciated.

I think it is not necessary. pg_dumpall supports dumping of the entire
contents of a database cluster,  It backs up each database in a given
cluster, and also *preserves cluster-wide data such as role and tablespace
definition*s. hence if you want to take backup for entire cluster then you
can directly use pg_dumpall.

or if you have any specific need then you can use pg_dump and manually
preserve/delete other database objects .


-----
Greetings, 
Samrat Revagade, 
NTT-DATA-OSS Center (Pune)
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Restore-after-using-pg-dumpall-tp5765452p5765716.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin