From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Eric Jain <eric(dot)jain(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Compression |
Date: | 2009-10-02 19:26:29 |
Message-ID: | 10263.1254511589@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Eric Jain <eric(dot)jain(at)gmail(dot)com> writes:
> So it looks like compression was supported in their commercial version
> of PostgreSQL. When it was discontinued, the people working on the
> open source version of PostgreSQL apparently didn't see any point in
> incorporating the code to support compression, so now there is none
> :-(
I seem to remember that that was discussed and the conclusion was that
it was reinventing the wheel --- you could perfectly well use ssl/ssh
compression if you needed it, and you'd want encryption too anyway
in most plausible scenarios where compression makes sense. (If the
network trip is long enough to justify compression, it's likely not
all secure.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Nicholson | 2009-10-03 21:28:46 | How do you batch insert and still obtain identity? |
Previous Message | Eric Jain | 2009-10-02 18:41:04 | Re: Compression |