| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Review: check existency of table for -t option (pg_dump) when pattern... |
| Date: | 2015-09-14 10:05:56 |
| Message-ID: | 55F69C04.5020203@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> (new version in attach), but patch shows some inconsistent output:
> % pg_dump -t 'aaa*' postgres
> pg_dump: No matching tables were found
> % pg_dump -t 'aaa*' --strict-names postgres
> pg_dump: Table "aaa*" not found.
> There are two different situation - first message says "there are not any table
> for work", second says "There are not specific table(s) with specific names
> (mask)". I am thinking so this information is enough interesting for showing.
Agree, but "aaa*" is not a table
>
> Can be changed to "No matching table(s) were found for filter "aaa*" " ?
"TBL" is not a filter. May be:
No matching table(s) were found for pattern "aaa*" ?
No matching table(s) were found for pattern "TBL" ?
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2015-09-14 10:07:05 | Re: Review: check existency of table for -t option (pg_dump) when pattern... |
| Previous Message | Tomas Vondra | 2015-09-14 09:53:02 | Re: On-demand running query plans using auto_explain and signals |