| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Subject: | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |
| Date: | 2018-07-27 17:56:32 |
| Message-ID: | CA+TgmoauJVv3i2E03OZN3Zf0QcQafXfW5v-AxrNnRmO9sZteaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 27, 2018 at 1:05 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> My point is more that it forces users to make choices whenever they use
> pg_dump. And the tar format has plenty downsides that aren't immediately
> apparent. By keeping something with only a small upside around, we
> force users to waste time.
Yeah, I admit that's a valid argument.
>> Why did we invent "custom" format dumps instead of using a standard
>> container-file format like tar/cpio/zip/whatever?
>
> Because they're either not all that simple, or don't random read access
> inside. But that's just a guess, not fact.
Mmm.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2018-07-27 17:59:12 | Re: How can we submit code patches that implement our (pending) patents? |
| Previous Message | Jonathan S. Katz | 2018-07-27 17:42:45 | Re: Explain buffers wrong counter with parallel plans |