| 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-03 12:02:02 |
| Message-ID: | CA+TgmoYcmh4EC61Um=akWrY0kaxk=7ifPA-S1LS_ka9k2eZC0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 3, 2018 at 6:31 AM, Surafel Temesgen <surafel3000(at)gmail(dot)com> wrote:
> On Mon, Jul 2, 2018 at 9:27 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> But you can specify multiple tables. You wouldn't want the same WHERE
>> clause to apply to all of them.
>>
> also with this new --where option you can specify multiple table using
> wildcard and it
> try to apply the same where clause to each table. may be its a desirable
> feature
> because such kind of table can be structurally similar too.
I don't think that's likely to be very useful. I think Carter Thaxton
has the right idea, although using foo:bar to mean foo.bar doesn't
seem like a great plan.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2018-07-03 12:15:46 | Re: pgsql: Clarify use of temporary tables within partition trees |
| Previous Message | Moon, Insung | 2018-07-03 11:48:10 | RE: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |