]> granicus.if.org Git - postgresql/commit
pg_dump: Strict names with no matching schema
authorStephen Frost <sfrost@snowman.net>
Tue, 10 Jan 2017 16:34:51 +0000 (11:34 -0500)
committerStephen Frost <sfrost@snowman.net>
Tue, 10 Jan 2017 16:34:51 +0000 (11:34 -0500)
commitabfd0095c1e1a2e3fad2696516b64871895334ec
treeb2a16d0575afc2f19ad3dd85d20e71d22ff78987
parent42f50cb8fa9848bbbc6776bcea03293a6b28b2d4
pg_dump: Strict names with no matching schema

When using pg_dump --strict-names and a schema pattern which doesn't
match any schemas (eg: --schema='nonexistant*'), we were incorrectly
throwing an error claiming no tables were found when, really, there
were no schemas found:

  -> pg_dump --strict-names --schema='nonexistant*'
  pg_dump: no matching tables were found for pattern "nonexistant*"

Fix that by changing the error message to say 'schemas' instead, since
that is what we are actually complaining about.

Noticed while testing pg_dump error cases.

Back-patch to 9.6 where --strict-names and this error message were
introduced.
src/bin/pg_dump/pg_dump.c