Re: BUG #7507: pg_restore silently fails when restoring a db with the --create flag and no user.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: iann(at)fuelforce(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7507: pg_restore silently fails when restoring a db with the --create flag and no user.
Date: 2012-08-27 19:31:08
Message-ID: 7536.1346095868@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

iann(at)fuelforce(dot)com writes:
> Attempting to restore a db using pg_restore to a new database server using
> the --create and --dbname flags fails silently if the db owner username does
> not exist in the new db or the -O flag is not used.
> Command used:
> pg_restore --create --verbose --dbname=testserver
> /Volumes/USBLINKS1/hostname.testserver.net_postgres_database

It'll fail, yes, because pg_dump by itself doesn't dump CREATE USER
commands (since users are external to any individual database).
However, it hardly seems "silent" to me. I see complaints like these:

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 1851; 1262 116736 DATABASE mydb dbowner
pg_restore: [archiver (db)] could not execute query: ERROR: role "dbowner" does not exist
Command was: ALTER DATABASE mydb OWNER TO dbowner;

pg_restore: [archiver (db)] Error from TOC entry 161; 1259 116737 TABLE mytable dbowner
pg_restore: [archiver (db)] could not execute query: ERROR: role "dbowner" does not exist
Command was: ALTER TABLE public.mytable OWNER TO dbowner;

WARNING: errors ignored on restore: 2

Possibly you want to use the --exit-on-error option?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2012-08-27 20:11:56 Re: Minor inheritance/check bug: Inconsistent behavior
Previous Message Bruce Momjian 2012-08-27 17:15:34 Re: BUG #6412: psql & fe-connect truncate passwords