From: | Radosław Smogura <rsmogura(at)softperience(dot)eu> |
---|---|
To: | Oguz Yilmaz <oguzyilmazlist(at)gmail(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: compression of query and result data in tcp socket connections |
Date: | 2011-09-05 11:28:33 |
Message-ID: | 7557d74651b14c357380938cfcdc8689@mail.softperience.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 5 Sep 2011 14:23:12 +0300, Oguz Yilmaz wrote:
> Hi,
>
> We need some handy method for compression of pgsql communication on
> port 5432. For my case, database is available over the internet and
> application logic has to reach the database remotely.
>
> I have searched for it and found those threads:
> http://archives.postgresql.org/pgsql-hackers/2002-05/msg00752.php
> http://archives.postgresql.org/pgsql-general/2010-08/msg00003.php
> http://archives.postgresql.org/pgsql-hackers/2002-03/msg00664.php
> http://archives.postgresql.org/pgsql-hackers/2006-05/msg01318.php
>
> Some suggested ssh tunneling for the compression as a wrapper.
> However
> this requires having to open ssh tunnels seperately for each remote
> db
> server. So this is not much handy for us.
No, there is no such support.
But if you don't want ssh, You may try IPSEC VPN for e.g. with IKEv2,
unless You are behind firewall compression may be enabled.
Regards,
Radosław Smogura
From | Date | Subject | |
---|---|---|---|
Next Message | Asia | 2011-09-05 12:07:00 | Re: SSL certificates issue |
Previous Message | Oguz Yilmaz | 2011-09-05 11:23:12 | compression of query and result data in tcp socket connections |