pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chad Robinson <taskswap@yahoo.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Problem with asynchronous connect in 8.0.1
Date: Mon, 07 Feb 2005 11:21:27 -0500
Message-ID: <27477.1107793287@sss.pgh.pa.us> (raw)
In-Reply-To: <20050207150504.14253.qmail@web11608.mail.yahoo.com>
References: <20050207150504.14253.qmail@web11608.mail.yahoo.com>

Chad Robinson <taskswap@yahoo.com> writes:
> I'm having a problem with asynchronous connections, and I can't seem to find
> a good example of this anywhere. To make things simple, I've reduced my
> program to the bare minimums, not even using select().

I believe that the async I/O code expects you to obey the API protocol,
in particular to wait for read-ready or write-ready where it says to.
Offhand I would expect an error return in case of failure to wait
long enough, though.

> In my Postgres logs I see:
>   LOG:  incomplete startup packet

Hmm, is it possible pqFlush never succeeded in writing out the whole
startup packet?  It'd be useful to look at the state of the connection
object with a debugger, esp. to see if anything is still pending in the
outbound I/O buffer.

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <27477.1107793287@sss.pgh.pa.us>
Permalink:  ../27477.1107793287@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27477.1107793287@sss.pgh.pa.us

 · 

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-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, taskswap@yahoo.com
  Subject: Re: Problem with asynchronous connect in 8.0.1
  In-Reply-To: <27477.1107793287@sss.pgh.pa.us>

* 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