Re: BUG #13804: pg_restore returns unexpected error - Mailing list pgsql-bugs

From michael@sqlexec.com
Subject Re: BUG #13804: pg_restore returns unexpected error
Date
Msg-id 566B46A2.8040105@sqlexec.com
Whole thread Raw
In response to Re: BUG #13804: pg_restore returns unexpected error  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Example Test Case:

psql
create database aaa;
\c aaa
create table t1(akey int);
insert into t1 VALUES(1);
\q

-- example generates exit code 1 for pg_restore when creating public schema
pg_dump    -d aaa      -p 6432 -C -c --if-exists -Fc -v -w -f  ./db.dump
pg_restore -d postgres -p 6432 -C -c --if-exists -Fc -v        ./db.dump

-- generate listing
pg_restore -C -c --if-exists -Fc -v -l db.dump > db.list

-- generate output commands (no db provided)
pg_restore -C -c --if-exists -Fc -v -L db.list db.dump

-- execute using the list: generates same exit code 1 when attempting to
create public schema
pg_restore -C -c --if-exists -Fc -v -L db.list db.dump -d postgres



> Michael Paquier <mailto:michael.paquier@gmail.com>
> Monday, December 7, 2015 7:06 PM
>
>
>
> If you think this is a bug, could you send a test case? There is not
> enough information regarding what you expect of pg_restore and what it
> is currently doing.
> --
> Michael

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type