diff options
| author | Stephen Frost <sfrost@snowman.net> | 2017-01-10 11:34:55 -0500 |
|---|---|---|
| committer | Stephen Frost <sfrost@snowman.net> | 2017-01-10 11:34:55 -0500 |
| commit | 22a85b3fbe85a9f1c92de90192de001b7394b4fe (patch) | |
| tree | 00e01cb9b3eed44080e0352e50e5dda563adcaca /src | |
| parent | 96f2344f381df94fcb9b84bffc58bbc540edd842 (diff) | |
| download | postgresql-22a85b3fbe85a9f1c92de90192de001b7394b4fe.tar.gz postgresql-22a85b3fbe85a9f1c92de90192de001b7394b4fe.zip | |
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.
Diffstat (limited to 'src')
| -rw-r--r-- | src/bin/pg_dump/pg_dump.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.c index efb369ff285..6e3d8473edb 100644 --- a/src/bin/pg_dump/pg_dump.c +++ b/src/bin/pg_dump/pg_dump.c @@ -1219,7 +1219,7 @@ expand_schema_name_patterns(Archive *fout, res = ExecuteSqlQuery(fout, query->data, PGRES_TUPLES_OK); if (strict_names && PQntuples(res) == 0) - exit_horribly(NULL, "no matching tables were found for pattern \"%s\"\n", cell->val); + exit_horribly(NULL, "no matching schemas were found for pattern \"%s\"\n", cell->val); for (i = 0; i < PQntuples(res); i++) { |