| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | Carter Thaxton <carter(dot)thaxton(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add --include-table-data-where option to pg_dump, to export only a subset of table data |
| Date: | 2018-09-06 13:18:32 |
| Message-ID: | CALAY4q8BY9SzjrG0UROuBg_0BXdCGab9dTteLgrLk01oqg5wNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 3, 2018 at 1:11 AM, Carter Thaxton <carter(dot)thaxton(at)gmail(dot)com>
wrote:
> The whole reason for the colon in the --where option is to indicate which
> table the WHERE clause should refer to, so that one can dump less than all
> of the rows.
> The --table option is totally different. It specifies which tables to
> dump at all.
>
Thank you for explaining,
I just have one comment . I found the error message generated on incorrect
where clause specification strange for pg_dump. I think query result status
check needed to handle it and generate more friendly error message.
regards
Surafel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2018-09-06 13:30:39 | Re: Funny hang on PostgreSQL 10 during parallel index scan on slave |
| Previous Message | Alexander Korotkov | 2018-09-06 12:58:00 | Re: [HACKERS] Bug in to_timestamp(). |