pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Harald Armin Massa <haraldarminmassa@gmail.com>
To: PFC <lists@peufeu.com>
Cc: Rainer Bauer <usenet@munnin.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Data transfer very slow when connected via DSL
Date: Fri, 22 Jun 2007 14:45:12 +0200
Message-ID: <7be3f35d0706220545uaaa957ey3b1ca083ba895c39@mail.gmail.com> (raw)
In-Reply-To: <op.tubj5nq5cigqcu@apollo13>
References: <s7tk73d57kvb3f4ph1kmkvhdfe0kak5a1r@4ax.com>
	<7be3f35d0706210801p732f2e73o147e3cbc0dc98153@mail.gmail.com>
	<d1el7392q4eab7uqud2ci3ihn2fqkusjms@4ax.com>
	<7be3f35d0706220324n1b8a41e1q7d235970044da689@mail.gmail.com>
	<op.tubj5nq5cigqcu@apollo13>

PFC,

> 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.
>

>       What about a SSH tunnel using data compression ?
Setup on multiple Windows Workstations in multiple Installations is not
possible.

> If you fetch all rows from a query in one go, would it be fast ?
I tried the same copy_to via VPN. It took 10-50x the time it took locally.

>Also, PG can now COPY from a query, so you don't really need the temp
table...
I know, but was stuck to 8.1 on some servers.

Best wishes,

Harald

-- 
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
fx 01212-5-13695179
-
EuroPython 2007 will take place in Vilnius, Lithuania from Monday 9th July
to Wednesday 11th July. See you there!

view thread (27+ messages)  latest in thread

Message-ID: <7be3f35d0706220545uaaa957ey3b1ca083ba895c39@mail.gmail.com>
Permalink:  ../7be3f35d0706220545uaaa957ey3b1ca083ba895c39@mail.gmail.com/
Also on:    postgresql.org/message-id/7be3f35d0706220545uaaa957ey3b1ca083ba895c39@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: haraldarminmassa@gmail.com, lists@peufeu.com, usenet@munnin.com
  Subject: Re: Data transfer very slow when connected via DSL
  In-Reply-To: <7be3f35d0706220545uaaa957ey3b1ca083ba895c39@mail.gmail.com>
  References: <s7tk73d57kvb3f4ph1kmkvhdfe0kak5a1r@4ax.com> <7be3f35d0706210801p732f2e73o147e3cbc0dc98153@mail.gmail.com> <d1el7392q4eab7uqud2ci3ihn2fqkusjms@4ax.com> <7be3f35d0706220324n1b8a41e1q7d235970044da689@mail.gmail.com> <op.tubj5nq5cigqcu@apollo13> <7be3f35d0706220545uaaa957ey3b1ca083ba895c39@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox