| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: db partial dumping with pg_dump |
| Date: | 2002-08-14 05:18:31 |
| Message-ID: | 5020.1029302311@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> What about a switch to set schema search path as well?
I'm leaning to the thought that this is a bad idea, and that pg_dump
should act in a way that's search-path-independent. But I need to
think more.
> You could also just have the tables comma separated in the -t ??
Don't like it --- that makes comma a special character in pg_dump
tablename patterns, which is an exception we don't need to make.
The multiple-dash-t approach needs no such assumption.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2002-08-14 05:19:54 | Re: Better handling of parse errors |
| Previous Message | Bruce Momjian | 2002-08-14 05:17:54 | Re: pg_stat_reset() weirdness |