Skip site navigation (1) Skip section navigation (2)

Peculiar behaviour in libpq

From: Tim Allen <tim(at)proximity(dot)com(dot)au>
To: pgsql-interfaces(at)hub(dot)org
Subject: Peculiar behaviour in libpq
Date: 1999-06-24 04:29:58
Message-ID: Pine.LNX.4.10.9906241349250.24932-100000@bee.proximity.com.au (view raw or flat)
Thread:
Lists: pgsql-interfaces
I've noticed some strange behaviour when using libpq with
PostgreSQL 6.4.2 on RedHat Linux 5.1. I'm using libpq asynchronously, with
a select() loop, calling PQconsumeInput etc. What is happening is that
occasionally, after I have received a callback via select() and processed
the result, I get an extra callback. These extra callbacks have no result
attached to them, PQisBusy() returns false, and, by the records I'm
keeping in my own program, there is no database operation pending (ie I
already have a result for every operation I've submitted).

I guess it's some sort of random noise on the socket or something. Or
maybe the backend just sends a nothing-in-particular packet down the line
every now and then. But I'm wondering if this is a symptom of something
else going wrong.

It tends to happen after several other operations, ie while the database
is reasonably busy, not when it's idle.

Has anyone else ever seen this behaviour? Is it anything to worry about?
Will it go away in 6.5? On the whole it seems reasonably benign, I just
worry there may be something bad going on that will bite me eventually.

Tim

-----------------------------------------------
Tim Allen
Proximity Pty Ltd  http://www.proximity.com.au
-----------------------------------------------


pgsql-interfaces by date

Next:From: Tom Ivar HelbekkmoDate: 1999-06-24 06:23:08
Subject: Re: [INTERFACES] Performance
Previous:From: Thomas LockhartDate: 1999-06-24 02:02:23
Subject: Re: [INTERFACES] Performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group