From: | raghu ram <raghuchennuru(at)gmail(dot)com> |
---|---|
To: | Asmus Reinhard <Reinhard(dot)Asmus(at)spdfraktion(dot)de> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Restore after using pg_dumpall |
Date: | 2013-07-29 13:33:47 |
Message-ID: | CALnrrJS75KM9rq8sEmWWTq-QZERh-H=vL=EMYP5es7Cvuxf=ZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Jul 29, 2013 at 6:49 PM, Asmus Reinhard <
Reinhard(dot)Asmus(at)spdfraktion(dot)de> wrote:
> Hallo,****
>
> ** **
>
> between****
>
> ** **
>
> pg_dumpall > alldb.sql (store)****
>
> ** **
>
>
According above command,you are taking all databases dump in plain text
format which are available in PostgreSQL cluster running on 5432 port
number.
and****
>
> ** **
>
> psql –f alldb.sql postgres (restore)****
>
> ** **
>
> is it necessary to drop existing objects (for example roles, …) ?****
>
>
According to above command,Restoring plain text dumpfile into
same PostgreSQL cluster running on 5432 port number.
If my assumptions are correct then you should drop existing database
objects.
Thanks & Regards
Raghu Ram
From | Date | Subject | |
---|---|---|---|
Next Message | German Becker | 2013-07-29 14:17:11 | Re: Disk latency goes up during certaing pediods |
Previous Message | Asmus Reinhard | 2013-07-29 13:19:30 | Restore after using pg_dumpall |