Re: PostgreSQL web site - Mailing list pgsql-www

From Magnus Hagander
Subject Re: PostgreSQL web site
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0FB7D@algol.sollentuna.se
Whole thread Raw
In response to Re: PostgreSQL web site  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: PostgreSQL web site  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: PostgreSQL web site  (Oleg Bartunov <oleg@sai.msu.su>)
Re: PostgreSQL web site  (Naz Gassiep <naz@mira.net>)
Re: PostgreSQL web site  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-www
> > Just a suggestion, why don't the web admins turn mod_gzip on? There
> > are no downsides, and it would likely make a fairly large impact on
> > bandwidth bills. Think of all the people browsing the PG
> documentation
> > (myself included). Not only would bandwidth bills go down,
> > responsiveness on the docs would be higher as well.
> >
> > Even if there is no bandwidth saving (if your b/w is free for
> > instance), I'm of the opinion that mod_gzip and mod_deflate
> should be
> > used unless there is a compelling reason not to.
> >
> > Sorry if this has been discussed before, but I thought it was worth
> > mentioning on the off chance it hadn't.
>
> Actually that is a very good question... why are we not using
> mod_deflate?

Good question. It's definitly worth investigating. It does add load to
the server, but not all that much. And if we have the space (need to
check that on some of the boxen) we could set up pre-compressed static
images and that argument would go away..

//Magnus

pgsql-www by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: PostgreSQL web site
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL web site