pg_dump quietly ignore missing tables - is it bug?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_dump quietly ignore missing tables - is it bug?
Date: 2015-03-13 15:26:05
Message-ID: CAFj8pRBW=V-8fPs8Xh0gzhf3_QO1D2-H3gepDNKZ5g9-h_tt1g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

we found possible bug in pg_dump. It raise a error only when all specified
tables doesn't exists. When it find any table, then ignore missing other.

/usr/local/pgsql/bin/pg_dump -t Foo -t omega -s postgres > /dev/null; echo
$?

foo doesn't exists - it creates broken backup due missing "Foo" table

[pavel(at)localhost include]$ /usr/local/pgsql/bin/pg_dump -t Foo -t omegaa
-s postgres > /dev/null; echo $?
pg_dump: No matching tables were found
1

Is it ok? I am thinking, so it is potentially dangerous. Any explicitly
specified table should to exists.

Regards

Pavel

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2015-03-13 15:41:19 Re: Reduce pinning in btree indexes
Previous Message Matthew McGuire 2015-03-13 15:14:15 Re: Fwd: Regarding pg_stat_statements