| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Chris Albertson <chrisalbertson90278(at)yahoo(dot)com>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, pgsql-general <pgsql-general(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Question: merit / feasibility of compressing frontend |
| Date: | 2002-07-16 05:47:46 |
| Message-ID: | 3521.1026798466@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> There is a real commercial need, when dealing with VPN's, remote
> users, and web based distributed applications for something like this.
This unsubstantiated opinion doesn't really do much to change my
opinion. We have seen maybe two or three prior requests for compression
(which does not qualify as a groundswell); furthermore they were all "it
would be nice if..." handwaving, with no backup data to convince anyone
that any real performance gain would emerge in common scenarios. So I'm
less than eager to buy into the portability and interoperability
pitfalls that are likely to emerge from requiring clients and servers to
have zlib.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-16 05:50:15 | Re: Question: merit / feasibility of compressing frontend |
| Previous Message | Tom Lane | 2002-07-16 05:38:46 | Re: table size growing out of control |