From: Rainer Bauer <usenet@munnin.com>
To: pgsql-performance@postgresql.org
Subject: Re: Data transfer very slow when connected via DSL
Date: Fri, 22 Jun 2007 11:15:12 +0200
Message-ID: <bq3n73t5u9i3o7bh3lbfqftee0aabaf35l@4ax.com> (raw)
References: <s7tk73d57kvb3f4ph1kmkvhdfe0kak5a1r@4ax.com>
<7be3f35d0706210801p732f2e73o147e3cbc0dc98153@mail.gmail.com>
<d1el7392q4eab7uqud2ci3ihn2fqkusjms@4ax.com>
<24rl73d5td717rimunndjnjghfl1pgqojh@4ax.com>
<10461.1182477071@sss.pgh.pa.us>
Hello Tom,
>This previous post says that someone else solved an ODBC
>performance problem with UseDeclareFetch=1:
I thought about that too, but enabling UseDeclareFetch will slow down the
query: it takes 30 seconds instead of 8.
>It's not immediately clear why pgAdmin would have the same issue,
>though, because AFAIK it doesn't rely on ODBC.
No it doesn't. That's the reason I used it to verify the behaviour.
But I remember Dave Page mentioning using a virtual list control to display
the results and that means a round trip for every tuple.
>I just finished looking through our archives for info about
>Windows-specific network performance problems.
I don't think it's a Windows-specific problem, because psql is doing the job
blindingly fast. The problem lies in the way my application is coded. See the
response to Dimitri for details.
Rainer
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: usenet@munnin.com
Subject: Re: Data transfer very slow when connected via DSL
In-Reply-To: <bq3n73t5u9i3o7bh3lbfqftee0aabaf35l@4ax.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