pgsql: Add emulation of non-blocking sockets to the win32 socket/signal

Started by Magnus Haganderover 16 years ago3 messagescomitters
Jump to latest
#1Magnus Hagander
magnus@hagander.net

Log Message:
-----------
Add emulation of non-blocking sockets to the win32 socket/signal layer,
and use this in pq_getbyte_if_available.

It's only a limited implementation which swithes the whole emulation layer
no non-blocking mode, but that's enough as long as non-blocking is only
used during a short period of time, and only one socket is accessed during
this time.

Modified Files:
--------------
pgsql/src/backend/libpq:
pqcomm.c (r1.202 -> r1.203)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqcomm.c?r1=1.202&r2=1.203)
pgsql/src/backend/port/win32:
socket.c (r1.23 -> r1.24)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/win32/socket.c?r1=1.23&r2=1.24)
pgsql/src/include/port:
win32.h (r1.92 -> r1.93)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/port/win32.h?r1=1.92&r2=1.93)

#2Thom Brown
thombrown@gmail.com
In reply to: Magnus Hagander (#1)
Re: pgsql: Add emulation of non-blocking sockets to the win32 socket/signal

On 16 February 2010 19:26, Magnus Hagander <mha@postgresql.org> wrote:

Log Message:
-----------
Add emulation of non-blocking sockets to the win32 socket/signal layer,
and use this in pq_getbyte_if_available.

It's only a limited implementation which swithes the whole emulation layer
no non-blocking mode, but that's enough as long as non-blocking is only
used during a short period of time, and only one socket is accessed during
this time.

Modified Files:
--------------
   pgsql/src/backend/libpq:
       pqcomm.c (r1.202 -> r1.203)
       (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqcomm.c?r1=1.202&amp;r2=1.203)
   pgsql/src/backend/port/win32:
       socket.c (r1.23 -> r1.24)
       (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/win32/socket.c?r1=1.23&amp;r2=1.24)

The pedant returns: s/thta/that/

   pgsql/src/include/port:
       win32.h (r1.92 -> r1.93)
       (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/port/win32.h?r1=1.92&amp;r2=1.93)

--

Thom

#3Magnus Hagander
magnus@hagander.net
In reply to: Thom Brown (#2)
Re: pgsql: Add emulation of non-blocking sockets to the win32 socket/signal

On Tue, Feb 16, 2010 at 20:32, Thom Brown <thombrown@gmail.com> wrote:

On 16 February 2010 19:26, Magnus Hagander <mha@postgresql.org> wrote:

Log Message:
-----------
Add emulation of non-blocking sockets to the win32 socket/signal layer,
and use this in pq_getbyte_if_available.

It's only a limited implementation which swithes the whole emulation layer
no non-blocking mode, but that's enough as long as non-blocking is only
used during a short period of time, and only one socket is accessed during
this time.

Modified Files:
--------------
   pgsql/src/backend/libpq:
       pqcomm.c (r1.202 -> r1.203)
       (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqcomm.c?r1=1.202&amp;r2=1.203)
   pgsql/src/backend/port/win32:
       socket.c (r1.23 -> r1.24)
       (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/port/win32/socket.c?r1=1.23&amp;r2=1.24)

The pedant returns: s/thta/that/

*sigh*. Thanks.

Can I get you to subscribe to my git branches and spellcheck
everything for me? ;)

Or more to the point, does anybody know a tool that will automatically
spellcheck your *comments* (and possibly also string contents),
without checking the actual code (and throwing errors on every line
bceause of C syntax)? Preferably able to deal with actual patch
output...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/