Re: Libpq Asynchronous Command Processing

From: Alonso García , Bruno Elier <bealonso(at)indra(dot)es>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Giles Lean <giles(dot)lean(at)pobox(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Libpq Asynchronous Command Processing
Date: 2010-05-31 16:31:27
Message-ID: 63A652C37EE6E04BA5234D623423FF97BBA06489D8@MADARRMAILBOX03.indra.es
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>So PQexec works fine for you on both 7.4 and 8.3, producing a quick
>result no matter which server you run it against?

Yes. If I use PQexec, both 7.4 and 8.3 produce a quick result but I if I use asynchronous command processing 8.3 produce a slow result whereas 7.4 works fine.

>Consider using wireshark to examine the network traffic, and see if
>there's much activity during your long and slow PQconsumeInput /
>PQisBusy loop. The throughput analysis tool is handy for this.
I will be back with the results.
Bruno,

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Viktor Pavlenko 2010-05-31 16:40:34 Trouble with timestamp in PQprepare/PQexecPrepared
Previous Message Isabella Ghiurea 2010-05-31 16:05:23 PG backup performance