From: | "michael(at)sqlexec(dot)com" <michael(at)sqlexec(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Cc: | pgdude(at)pgdude(dot)com, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Subject: | Re: BUG #13804: pg_restore returns unexpected error |
Date: | 2015-12-11 21:56:50 |
Message-ID: | 566B46A2.8040105@sqlexec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)paquier(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-12-11 22:30:25 | Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type |
Previous Message | Alvaro Herrera | 2015-12-11 21:54:45 | Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type |