Re: pgkill on win32

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: James Mansion <james(at)mansionfamily(dot)plus(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgkill on win32
Date: 2008-04-22 07:54:35
Message-ID: 20080422095435.622f8d78@mha-laptop
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout wrote:
> On Mon, Apr 21, 2008 at 09:47:02AM +0200, Magnus Hagander wrote:
> > Uh, sorry, got that explained backwards.
> > The problem is when winsock operations are interrupted by APCs.
> >
> > See:
> > http://archives.postgresql.org/pgsql-hackers-win32/2004-04/msg00013.php
>
> WRT this bit:
> > (1) carries a big problem - if we do this, we can *not* support SSL
> > on win32, because it uses recv() and send() internally (inside the
> > openssl library). Therefor, I don't think (1) is really an option -
> > at least not in the long run.
>
> openssl does not have to use recv/send, that's what the BIO
> infrastructure is for. The current backend code already constructs
> BIOs for reading to support interrupting (see my_sock_read), so you
> could replace the read with any functions you wanted.

Yes, it's on my TODO list to do just that. Unless this means you are
volunteering to do it? ;)

//Magnus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-04-22 07:56:08 Re: pgkill on win32
Previous Message Martijn van Oosterhout 2008-04-22 07:53:07 Re: pgkill on win32