non blcoking behaviour

From: Erik Hofman <erik(at)ehofman(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: non blcoking behaviour
Date: 2001-02-23 13:56:45
Message-ID: 3A966C1D.86415240@ehofman.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Erik Hofman
Your email address : erik(at)ehofman(dot)com

System Configuration
---------------------
Architecture (example: Intel Pentium) : SGI O2 / Mips RM5200

Operating System (example: Linux 2.0.26 ELF) :Irix 6.5.9

PostgreSQL version (example: PostgreSQL-7.0): PostgreSQL-7.0.3

Compiler used (example: gcc 2.8.0) : MipsPro C 7.3

Please enter a FULL description of your problem:
------------------------------------------------

I'm programming PostgreSQL using the non blocking function right now,
but i had a real struggle with it :(

The PQstatus returns CONNECTION_MADE, but PQsendQuery only checks for
CONNECTION_OK.
So PQsendQuery doesn't send the query, while i think that after
CONNECTION_MADE the query could be sent also.

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------

Probably adding CONNECTION_MADE to PQsendQuery

Erik

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Leonid Furman 2001-02-23 17:04:28 delete fails due to referential integrity, but return code is 0.
Previous Message Samuel Minne 2001-02-23 13:40:38 Re: Sequence of characters not supported by psql/pg_dump