| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
| Cc: | Carter Thaxton <carter(dot)thaxton(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>, Pg 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-07-02 18:27:20 |
| Message-ID: | CA+TgmobNq2DDdP6Sxe7mVbDomtZv83HP2dtKfE82VMaqQpndyw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 29, 2018 at 8:09 AM, Surafel Temesgen <surafel3000(at)gmail(dot)com> wrote:
> hey,
> i am reviewing this patch
> On Thu, May 31, 2018 at 4:49 AM, Carter Thaxton <carter(dot)thaxton(at)gmail(dot)com>
> wrote:
>>
>>
>> pg_dump --where '"foo:bar":created_at >= '2018-05-01'" dbname
>
> it would be more sqlish if it specified like:
> --table=foo --where ="bar created_at >= 2018-05-01"
> and i don't like the idea of duplicating the existing --table behavior it
> may confuse user
> i rather recommend extending it. And when i test it with --table option the
> content of dump
> file depend on the option specified first.
But you can specify multiple tables. You wouldn't want the same WHERE
clause to apply to all of them.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-07-02 18:43:04 | Re: Unexpected behavior of DROP VIEW/TABLE IF EXISTS |
| Previous Message | Robert Haas | 2018-07-02 18:25:58 | Re: shared-memory based stats collector |