| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | Carter Thaxton <carter(dot)thaxton(at)gmail(dot)com> |
| Cc: | 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-06-29 12:09:44 |
| Message-ID: | CALAY4q8NETGrT=vGtC7N1z6WV2gcc4HVkCv69PQAQ50eNzgNtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 사이트 추천SQL |
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.
Regards
Surafel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-06-29 12:19:26 | Re: Tips on committing |
| Previous Message | Peter Eisentraut | 2018-06-29 12:04:07 | Re: Tips on committing |