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

Re: [patch] helps fe-connect.c handle -EINTR more gracefully

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Ford <david(at)blue-labs(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [patch] helps fe-connect.c handle -EINTR more gracefully
Date: 2001-10-27 16:46:11
Message-ID: 2673.1004201171@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
David Ford <david(at)blue-labs(dot)org> writes:
>  I traced several calls and they run through a few functions which end 
> up in pqFlush.  These code paths haven't checked the socket to see if it 
> is ready for RW operation yet.  pqFlush calls send() [ignoring SSL].

Where?  AFAICS (ignoring the USE_SSL breakage), connectDBStart will
return immediately after calling connect(), and the next thing
that's done is pqWait from connectDBComplete.  If there's a path that
does what you claim, that's a bug ... but I don't see it.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-10-27 17:11:32
Subject: Re: consistent naming of components
Previous:From: mlwDate: 2001-10-27 14:20:58
Subject: Some suggestions.

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