| From: | Carter Thaxton <carter(dot)thaxton(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Surafel Temesgen <surafel3000(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 08:46:33 |
| Message-ID: | CAGiT_HNKeWDK9YFUMS1vct5XSchM+kK=Fa+bJ8c8WTpeFpJFDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
> > pg_dump --where "bar:created_at >= 2018-05-01'"
>
> I am wondering how this works at parsing if the table name, or one of
> the columns includes a colon character :)
>
The proposed patch will handle quoted identifiers. E.g. the following will
work just fine:
pg_dump --where 'table:"column:with:colons" = 5'
Note the use of single quotes in the shell, and then double quotes in the
WHERE clause. There are also many other options for quoting in the shell,
of course.
> Please don't top-post on the PostgreSQL lists. See <
http://idallen.com/topposting.html>
Sorry. Thanks for the reminder.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-07-03 08:49:11 | Re: pgsql: Clarify use of temporary tables within partition trees |
| Previous Message | Masahiko Sawada | 2018-07-03 08:27:07 | Re: Copy function for logical replication slots |