diff options
| author | Stephen Frost <sfrost@snowman.net> | 2017-01-10 11:34:51 -0500 |
|---|---|---|
| committer | Stephen Frost <sfrost@snowman.net> | 2017-01-10 11:34:51 -0500 |
| commit | abfd0095c1e1a2e3fad2696516b64871895334ec (patch) | |
| tree | b2a16d0575afc2f19ad3dd85d20e71d22ff78987 /src/backend/executor/execParallel.c | |
| parent | 42f50cb8fa9848bbbc6776bcea03293a6b28b2d4 (diff) | |
| download | postgresql-abfd0095c1e1a2e3fad2696516b64871895334ec.tar.gz postgresql-abfd0095c1e1a2e3fad2696516b64871895334ec.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/backend/executor/execParallel.c')
0 files changed, 0 insertions, 0 deletions