BUG #12750: issue with pg_restore s exit code when warnings are there - Mailing list pgsql-bugs

From trasnaramesh@gmail.com
Subject BUG #12750: issue with pg_restore s exit code when warnings are there
Date
Msg-id 20150209073351.15321.63830@wrigleys.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      12750
Logged by:          Rasna
Email address:      trasnaramesh@gmail.com
PostgreSQL version: 9.3.5
Operating system:   Linux
Description:



commands:

bin/pg_dump -b -o -Fc -Z 0 -p 5333 -U user template1 -f db.dump
bin/pg_restore -c  -h localhost -p 5333 -U user -d template1 db.dump

steps followed:

    add new tables to DB and took dump

    delete the newly added tables

    try restore with dump file

    restore exited with code 1 but still tables are restore successfully.

    error in pg_restore:
    pg_restore: [archiver (db)] could not execute query: err-1: table
"test1" does not exist
    Command was: DROP TABLE public.test1;
    WARNING: errors ignored on restore: 2

Is this the expected behavior for dump/restore feature with tables
add/delete steps?

Why pg_restore exit code is 1 when warning are there?

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #12746: Backward compatibility is broken 9.2: pg_stat_activity.procpid renamed to pid
Next
From: gianni.ciolli@2ndquadrant.it
Date:
Subject: BUG #12752: Regression in ALTER TABLE RENAME COLUMN