Re: BUG #4127: pg_dumpall -c unable to be restored without error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4127: pg_dumpall -c unable to be restored without error
Date
Msg-id 585.1209055454@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4127: pg_dumpall -c unable to be restored without error  ("Jacob Champlin" <jacobc@rentec.com>)
Responses Re: BUG #4127: pg_dumpall -c unable to be restored without error  (Jacob Champlin <jacobc@rentec.com>)
List pgsql-bugs
"Jacob Champlin" <jacobc@rentec.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

pgsql-bugs by date:

Previous
From: "Jacob Champlin"
Date:
Subject: BUG #4127: pg_dumpall -c unable to be restored without error
Next
From: Jacob Champlin
Date:
Subject: Re: BUG #4127: pg_dumpall -c unable to be restored without error