| From: | "Daniel R(dot) Anderson" <dan(at)mathjunkies(dot)com> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Cc: | pgsql-general-user(at)postgresql(dot)org | 
| Subject: | Re: PostgreSQL downloads compressed with bzip2 instead of | 
| Date: | 2003-03-20 12:44:39 | 
| Message-ID: | 1048164280.11212.10.camel@ny-chicagostreet2c-110.buf.adelphia.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
 <snip> 
> I know that for many people, file size is not much of an issue, 
> but for many others I suspect it is. Whether that is for reasons 
> of storage space on smaller drives, like on current laptops, or 
> older machines.
Point of Information:
Improved compression efficiency does not help people with small drives. 
Case in point: imagine sometime in the future a "supertarball" algorithm
is discovered.  This wondrous new algorithm compresses terabytes of data
into a single bit.  (Don't ask how -- the deranged computer scientist
who discovered it, went crazy doing so.  You might be next!)  
So Joe User boots up his trusty 386 with a 500MB hard drive, and dials
into AOL with a 9600 baud modem.  He grabs postgresql-7.3.3.SUPERTARBALL
off the 'net, and types into his console (since he doesn't have enough
processing power to run a modern version of windows):
$ supertarball -xvf postgresql-7.3.3.SUPERTARBALL
And Joe User runs out of disk space.
Moral of the Story:
A smaller file to download (via better compression) only decreases the
time it takes to download.  
:-D
-- 
Daniel R. Anderson
Great Lakes Industries, Inc.
80 Pineview Ave.
Buffalo, NY 14218
(716) 691-5900 x218
"Never let your schooling interfere with your education"
	-- Mark Twain
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miguel Carvalho | 2003-03-20 12:55:05 | Re: Trigger issue, bug? on 7.2.1 | 
| Previous Message | Olleg Samojlov | 2003-03-20 11:34:31 | Re: About tcp connection |