| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Paul Ramsey <pramsey(at)refractions(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org, "'gleeming(at)refractions(dot)net'" <gleeming(at)refractions(dot)net> |
| Subject: | Re: pg_dump "all tables" in 7.3.X |
| Date: | 2003-06-26 18:12:18 |
| Message-ID: | 1434.1056651138@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Paul Ramsey <pramsey(at)refractions(dot)net> writes:
> What the old 7.2 behavior gave us was the ability to dump all tables and
> views, but not dump all the functions and triggers. Is there an
> equivalent to that behavior still around?
Not at the moment. It would be a fine project to add more selectivity
options to pg_dump.
I wouldn't even object to reintroducing * into -t, if it were done
properly (ie, a real wild-card-match implementation, and not just a
two-line kluge that handles the one case) ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gould | 2003-06-26 18:12:32 | python script for crosstab queries in PostgreSQL |
| Previous Message | scott.marlowe | 2003-06-26 18:08:41 | Re: MS Access, pgsqlODBC and PostgreSQL in Linux via |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gould | 2003-06-26 18:14:05 | Re: pg_dump "all tables" in 7.3.X |
| Previous Message | Tom Lane | 2003-06-26 18:08:21 | Re: [GENERAL] pg_dump "all tables" in 7.3.X |