Well, it occurred to me that if a large result set were to be identified
before transport between a client and server, a significant amount of
bandwidth may be saved by using a moderate level of compression.
Especially with something like result sets, which I tend to believe may
lend it self well toward compression.
Unlike FTP which may be transferring (and often is) previously
compressed data, raw result sets being transfered between the server and
a remote client, IMOHO, would tend to compress rather well as I doubt
much of it would be true random data.
This may be of value for users with low bandwidth connectivity to their
servers or where bandwidth may already be at a premium.
The zlib exploit posting got me thinking about this.
Greg
On Thu, 2002-03-14 at 12:20, Bruce Momjian wrote:
> Greg Copeland wrote:
> > Just curious, and honestly I haven't looked, but is there any form of
> > compression between clients and servers? Has this been looked at?
>
> This issues has never come up before. It is sort of like compressing an
> FTP session. No one really does that. Is there value in trying it with
> PostgreSQL?
>
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026