From: Ronald Hahn, DOCFOCUS INC. <rhahn@docfocus.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Result Set over Network Question
Date: Thu, 03 May 2012 09:28:44 -0600
Message-ID: <4FA2A42C.9090900@docfocus.ca> (raw)
In-Reply-To: <CAHyXU0wdmbGNQgqwBVZR5UY6Nmb3-L6LSi+XA+gjMtqMFn-3Ww@mail.gmail.com>
References: <4F9EDACA.4010901@docfocus.ca>
<CAHyXU0wdmbGNQgqwBVZR5UY6Nmb3-L6LSi+XA+gjMtqMFn-3Ww@mail.gmail.com>
After some testing using wiershark (poor mans profiler) to see what was
going on with the network I found that it was the tools I've been using.
Both Aqua and PGadminIII have a large overhead per column to get the
meta data. MSSQL sends that data upfront so the impact isn't as bad. I'm
not sure if it's a limitation of the pgsql protocol vs tds or a
limitation of Aqua or a combination of both. At any rate it turns out
not to be part of the problem I'm having with my software stalling out
so I'm back to Square one with my problem.
Thanks,
Ron
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: rhahn@docfocus.ca
Subject: Re: Result Set over Network Question
In-Reply-To: <4FA2A42C.9090900@docfocus.ca>
* 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