Skip site navigation (1) Skip section navigation (2)

Re: BUG #4127: pg_dumpall -c unable to be restored without error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jacob Champlin" <jacobc(at)rentec(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4127: pg_dumpall -c unable to be restored without error
Date: 2008-04-24 16:44:14
Message-ID: 585.1209055454@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Jacob Champlin" <jacobc(at)rentec(dot)com> writes:
> psql -f restore.sql

> results in:

> psql:/var/lib/pgsql/backups/restore.sql:11: ERROR:  current user cannot be
> dropped
> psql:/var/lib/pgsql/backups/restore.sql:12: ERROR:  role "postgres" already
> exists
> psql:/var/lib/pgsql/backups/restore.sql:17: ERROR:  role "webapp" cannot be
> dropped because some objects depend on it
> DETAIL:  access to database rief
> 113 objects in database rief
> psql:/var/lib/pgsql/backups/restore.sql:18: ERROR:  role "webapp" already
> exists

And?  The restore would've proceeded anyway.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Jacob ChamplinDate: 2008-04-24 17:04:43
Subject: Re: BUG #4127: pg_dumpall -c unable to be restored without error
Previous:From: Jacob ChamplinDate: 2008-04-24 16:37:10
Subject: BUG #4127: pg_dumpall -c unable to be restored without error

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group