| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ivan Lezhnjov IV <iliv(at)commandprompt(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backup.sgml patch that adds information on custom format backups |
| Date: | 2013-02-10 21:47:46 |
| Message-ID: | 1360532866.34615.YahooMailNeo@web162903.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I'm not sure what others think, but the proposed wording seems a
> bit hard on plain text dumps to me.
Agreed. I don't know how many times I've piped the output of
pg_dump to the input of psql. Certainly that was very common
before pg_upgrade was available. And for development purposes a
text script file is often exactly what is needed -- to store it in
custom format first would just be an extra step which would waste
time. Since I got my head around PITR dumps, I've rarely had a
reason to use the pg_dump custom format, myself.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-02-10 22:15:23 | Re: backup.sgml patch that adds information on custom format backups |
| Previous Message | Phil Sorber | 2013-02-10 21:03:38 | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) |