| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | James William Pye <pgsql(at)jwp(dot)name>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: rfc: add pg_dump options to dump output |
| Date: | 2008-06-05 00:20:23 |
| Message-ID: | Pine.GSO.4.64.0806042017260.3874@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 3 Jun 2008, Tom Lane wrote:
> Well, the stuff included into the dump by pg_dump -v is informative,
> too. But we stopped doing that by default because of complaints.
> I remain unconvinced that this proposal won't suffer the same fate.
I think it would be reasonable to only include the list of options used in
the dump if you use one that changes what appears in the dump. That way,
you wouldn't see anything by default. But if you make a modification that
will likely break a diff with an existing dump done with the default
parameters, the option change that introduced that should show at the very
beginning.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-05 00:23:17 | Re: Overhauling GUCS |
| Previous Message | Greg Smith | 2008-06-05 00:16:55 | Re: Overhauling GUCS |