| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, daveg <daveg(at)sonic(dot)net>, Andrew Chernow <ac(at)esilo(dot)com>, Dann Corbit <DCorbit(at)connx(dot)com>, Stanislav Lacko <lacko(at)spacesystems(dot)sk>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is a plan for lmza commpression in pg_dump |
| Date: | 2009-02-08 15:06:35 |
| Message-ID: | 498EF4FB.2080605@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
>
> Why don't we just add an option to pg_dump --use-compress-program, just
> like tar and then people can use their "compression algorithm of the
> week" and we don't need to care about the licence or anything.
>
> It's not like the case of TOAST where it actually needs to be builtin.
> Tar doesn't have any compression builtin, yet you don't see many
> uncompressed tar files...
>
>
>
tar compresses/decompresses the whole archive via a single pipe. pg_dump
compresses individual data members. If the compression isn't builtin it
will make life much more difficult, and probably make parallel restore
as well as some other operations well nigh impossible.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-08 16:13:47 | WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
| Previous Message | Andrew Chernow | 2009-02-08 14:59:43 | Re: Is a plan for lmza commpression in pg_dump |