| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Carter Thaxton <carter(dot)thaxton(at)gmail(dot)com> |
| Subject: | pg_dump --where option |
| Date: | 2020-06-15 20:26:13 |
| Message-ID: | CALAY4q8o00Sg5nemi2AuqNuLvmGLaR6br+YrvM41ZuSPjM2Qvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Internally pg_dump have capability to filter the table data to dump by same
filter clause but it have no interface to use it and the patch here [1]
adds interface to it but it have at-least two issue, one is error message
in case of incorrect where clause specification is somehow hard to debug
and strange to pg_dump .Other issue is it applies the same filter clause to
multiple tables if pattern matching return multiple tables and it seems
undesired behavior to me because mostly we don’t want to applied the same
where clause specification to multiple table. The attached patch contain a
fix for both issue
regards
Surafel
| Attachment | Content-Type | Size |
|---|---|---|
| pg_dump_where_clause-v1.patch | text/x-patch | 12.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-06-15 20:49:04 | Re: tar-related code in PostgreSQL |
| Previous Message | Daniel Gustafsson | 2020-06-15 19:04:07 | Re: language cleanups in code and docs |