Re: PostgreSQL downloads compressed with bzip2 instead of - Mailing list pgsql-general

From greg@turnstep.com
Subject Re: PostgreSQL downloads compressed with bzip2 instead of
Date
Msg-id 1d150e981ebab6162f5cd86a1e87034f@biglumber.com
Whole thread Raw
In response to Re: PostgreSQL downloads compressed with bzip2 instead of  ("Daniel R. Anderson" <dan@mathjunkies.com>)
Responses Re: PostgreSQL downloads compressed with bzip2 instead of  ("Daniel R. Anderson" <dan@mathjunkies.com>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Moral of the Story:
>
> A smaller file to download (via better compression) only decreases the
> time it takes to download.

I think the real argument in favor of providing a bz2 alternative to gz
*is* the time to download. Loading a Postgres tarball over a dialup line
is much faster with bz2 rather than gz. This has been covered on the list
before: I recall that most everyone agreed it was a good idea, but nobody
on the website appeared ready to follow through with it and actually
set up the bz2 files.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200303201036
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+eeCfvJuQZxSWSsgRAvy+AJ9wWoOgXezn3p01/D4jed2sNqT6DQCfXkz5
0uvv7khQJ4LAXMYydMnpWdM=
=Lg8Y
-----END PGP SIGNATURE-----



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: transaction problem (delete/select/insert sequence fails, a bug?)
Next
From: Tom Lane
Date:
Subject: Re: Big insert/delete memory problems