| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |
| Date: | 2018-07-27 18:12:45 |
| Message-ID: | 87va90blc4.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Andres" == Andres Freund <andres(at)anarazel(dot)de> writes:
>> Why did we invent "custom" format dumps instead of using a standard
>> container-file format like tar/cpio/zip/whatever?
Andres> Because they're either not all that simple, or don't random
Andres> read access inside. But that's just a guess, not fact.
A more significant factor is that tar (like most file archive formats)
doesn't allow streamed _write_ access - you need to know the size of
each archive member in advance, hence why -Ft has to copy each table to
a temp file and then copy that into the archive.
--
Andrew.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-07-27 18:13:07 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |
| Previous Message | Tom Lane | 2018-07-27 18:12:06 | Re: Deprecating, and scheduling removal of, pg_dump's tar format. |