Re: bad examples in pg_dump README
От | Josh Kupershmidt |
---|---|
Тема | Re: bad examples in pg_dump README |
Дата | |
Msg-id | CAK3UJRFqgYYT1Gqk=UrwwpRvu9_K3fv857_BdvO40VnfVHKH0g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: bad examples in pg_dump README (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: bad examples in pg_dump README
|
Список | pgsql-hackers |
On Mon, Jan 7, 2013 at 8:12 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > On Sat, 2013-01-05 at 15:34 +0100, Magnus Hagander wrote: >> On Fri, Jan 4, 2013 at 3:36 AM, Josh Kupershmidt <schmiddy@gmail.com> wrote: >> > I propose slimming down the pg_dump README, keeping intact the >> > introductory notes and details of the tar format. >> >> Do we need to keep it at all, really? Certainly the introductory part >> is covered in the main documentation already... > > I'd remove it and distribute the remaining information, if any, between > the source code and the man page. Here's a patch to do so. After removing the discussed bogus information, there were only two notes which I still found relevant, so I stuck those in the appropriate header comments. I didn't preserve the comment about "blank username & group" for tar'ed files, since there are already some comments along these lines in tarCreateHeader(), and these are "postgres" not "blank" nowadays. The pg_dump/pg_restore man pages seemed to already do a good enough job of showing usage examples that I didn't find anything worth adding there. Josh
Вложения
В списке pgsql-hackers по дате отправления: