Re: Deprecating, and scheduling removal of, pg_dump's tar format. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Deprecating, and scheduling removal of, pg_dump's tar format.
Date
Msg-id CA+TgmoauJVv3i2E03OZN3Zf0QcQafXfW5v-AxrNnRmO9sZteaw@mail.gmail.com
Whole thread Raw
In response to Re: Deprecating, and scheduling removal of, pg_dump's tar format.  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, Jul 27, 2018 at 1:05 PM, Andres Freund <andres@anarazel.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


pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: Explain buffers wrong counter with parallel plans
Next
From: Chapman Flack
Date:
Subject: Re: How can we submit code patches that implement our (pending)patents?