Re: walreceiver is uninterruptible on win32 - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: walreceiver is uninterruptible on win32
Date
Msg-id 9837222c1003120313l2a1ec911vaf229a4f7890f010@mail.gmail.com
Whole thread Raw
In response to walreceiver is uninterruptible on win32  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: walreceiver is uninterruptible on win32
List pgsql-hackers
On Wed, Mar 10, 2010 at 10:09, Fujii Masao <masao.fujii@gmail.com> wrote:
> Hi,
>
> http://archives.postgresql.org/pgsql-hackers/2010-01/msg01672.php
> On win32, the blocking libpq functions like PQconnectdb() and
> PQexec() are uninterruptible since they use the vanilla select()
> instead of our signal emulation layer compatible select().
> Nevertheless, currently walreceiver uses them to establish a
> connection, send a handshake message and wait for the reply.
> So walreceiver also becomes uninterruptible for a while. This
> is the must-fix problem for 9.0.
>
> I replaced the blocking libpq functions currently used with
> asynchronous ones, and used the emulated version of select()
> to wait, to make walreceiver interruptible. Here is the patch.

These are issues that affect other things running libpq in the backend
as well, right? Such as dblink? Perhaps we can factor out most of this
into functions in backend/port/win32 so that we can re-use it fro
there?


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


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [patch] build issues on Win32
Next
From: Merlin Moncure
Date:
Subject: Re: Dyamic updates of NEW with pl/pgsql