Date: Fri, 22 Jun 2007 12:45:13 +0200
To: "Harald Armin Massa" <haraldarminmassa@gmail.com>,
	"Rainer Bauer" <usenet@munnin.com>
Subject: Re: Data transfer very slow when connected via DSL
From: PFC <lists@peufeu.com>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <s7tk73d57kvb3f4ph1kmkvhdfe0kak5a1r@4ax.com>
	<7be3f35d0706210801p732f2e73o147e3cbc0dc98153@mail.gmail.com>
	<d1el7392q4eab7uqud2ci3ihn2fqkusjms@4ax.com>
	<7be3f35d0706220324n1b8a41e1q7d235970044da689@mail.gmail.com>
Content-Transfer-Encoding: 7bit
Message-ID: <op.tubj5nq5cigqcu@apollo13>
In-Reply-To: <7be3f35d0706220324n1b8a41e1q7d235970044da689@mail.gmail.com>
User-Agent: Opera Mail/9.21 (Linux)


>> I did not find a solution so far; and for bulk data transfers I now
>> >programmed a workaround.
>>
>> But that is surely based on some component installed on the server,  
>> isn't
>> it?
>>
>
> Correct. I use a pyro-remote server. On request this remote server copies
> the relevant rows into a temporary table, uses a copy_to Call to push  
> them
> into a StringIO-Objekt (that's Pythons version of "In Memory File"),
> serializes that StringIO-Objekt, does a bz2-compression and transfers the
> whole block via VPN.
>
> I read on in this thread, and I scheduled to check on psycopg2 and what  
> it is doing with cursors.

	What about a SSH tunnel using data compression ?
	If you fetch all rows from a query in one go, would it be fast ?
	Also, PG can now COPY from a query, so you don't really need the temp  
table...