Re: Proposal: new pg_dump options --copy-delimiter and
От | Andrew Dunstan |
---|---|
Тема | Re: Proposal: new pg_dump options --copy-delimiter and |
Дата | |
Msg-id | 1138389476.3074.39.camel@swithin обсуждение исходный текст |
Ответ на | Re: Proposal: new pg_dump options --copy-delimiter and (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Fri, 2006-01-27 at 14:08 -0500, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: > > On Fri, 2006-01-27 at 13:43 -0500, Tom Lane wrote: > >> That line of argument leads to the suggestion that pg_dump should just > >> use something else (I'd vote for "|"), all the time, in order to produce > >> more robust dump files. I still don't see the argument for exposing > >> a switch though. > > > If we regard them as suitable for human editing for normal use, yes. > > No, that actually was no part of my point. A pg_dump file that doesn't > use tabs is more likely to survive being emailed, for instance. I'm not > sure whether that is a large enough consideration to justify a change, > but you don't have to assume that anyone's intending to edit anything > to make the argument for it. > Not sure how much that matters in these days of MIME, but it's a fair point nevertheless. cheers andrew
В списке pgsql-hackers по дате отправления: