Rewriting backup.sgml (patch attached) - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Rewriting backup.sgml (patch attached)
Date
Msg-id 555BAB82.3080803@commandprompt.com
Whole thread Raw
Responses Re: Rewriting backup.sgml (patch attached)  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Hello,

Alright, per previous discussions I went through the backup.sgml page. I
have gone thoroughly through:

sql dump
pg_dump
pg_restore
handling large databases

I removed file based backups

I didn't really touch the red headed step child that is pg_dumpall
(although a word smithed it a little).

I tried to remove some of the conversationalist tone. This is technical
documentation not a story. I also removed as many extra words as
reasonable and added specific examples.

Now, I know some of you will say things like... why did you add -C to
the pg_dump line. The reason is simple, without it as new person is
going to get an error on restore. Our documentation should be explicit
not implicit.

I do not want to progress any farther on this until I get some feedback.

Sincerely,

JD
--
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.

Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Problems with question marks in operators (JDBC, ECPG, ...)