pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Richard Huxton <dev@archonet.com>
To: Werner Scholtes <Werner.Scholtes@heuboe.de>
Cc: Divakar Singh <dpsmails@yahoo.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: performance libpq vs JDBC
Date: Thu, 16 Dec 2010 12:14:32 +0000
Message-ID: <4D0A02A8.5050206@archonet.com> (raw)
In-Reply-To: <128DB53227227D43B4AAEED73E89A81901E2C4B58B@vm-exchg-2k8.heuboe.hbintern>
References: <128DB53227227D43B4AAEED73E89A81901E2C4B584@vm-exchg-2k8.heuboe.hbintern>
<209185.49892.qm@web65409.mail.ac4.yahoo.com>
<128DB53227227D43B4AAEED73E89A81901E2C4B58B@vm-exchg-2k8.heuboe.hbintern>
On 16/12/10 09:21, Werner Scholtes wrote:
> I assume that the wire protocol of PostgreSQL allows to transmit
> multiple rows at once, but libpq doesn't have an interface to access it.
> Is that right?
Sounds wrong to me. The libpq client is the default reference
implementation of the protocol. If there were large efficiencies that
could be copied, they would be.
Anyway - you don't need to assume what's in the protocol. It's
documented here:
http://www.postgresql.org/docs/9.0/static/protocol.html
I'd stick wireshark or some other network analyser on the two sessions -
see exactly what is different.
--
Richard Huxton
Archonet Ltd
view thread (10+ messages) latest in thread
Message-ID: <4D0A02A8.5050206@archonet.com> Permalink: ../4D0A02A8.5050206@archonet.com/ Also on: postgresql.org/message-id/4D0A02A8.5050206@archonet.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 using the --to and --cc options: reply via email To: pgsql-performance@postgresql.org Cc: dev@archonet.com, Werner.Scholtes@heuboe.de, dpsmails@yahoo.com Subject: Re: performance libpq vs JDBC In-Reply-To: <4D0A02A8.5050206@archonet.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