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

From Magnus Hagander
Subject Re: walreceiver is uninterruptible on win32
Date
Msg-id t2l9837222c1004190711n7d3e3c7cy4601c646f367de9@mail.gmail.com
Whole thread Raw
In response to Re: walreceiver is uninterruptible on win32  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Fri, Apr 16, 2010 at 09:03, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Thu, Apr 15, 2010 at 11:26 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> I have to admit to finding this confusing.  According to the comments:
>>
>> +               /*
>> +                * Don't emulate the PQexec()'s behavior of returning the last
>> +                * result when there are many, since walreceiver never sends a
>> +                * query returning multiple results.
>> +                */
>>
>> ...but it looks like the code actually is implementing some sort of
>> loop-that-returns-the-last result.
>
> Yeah, it's not a very accurate description. And I found another problem:
> libpqrcv_PQexec() ends as soon as an error result arrives even if its
> state has not been PGASYNC_IDLE yet.
>
> So I changed libpqrcv_PQexec() so that it emulates the PQexec()'s behavior
> except the concatenation of error messages. How about the attached patch?

Applied with only minor stylistic changes. Thanks!

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CTAS not honoring NOT NULL, DEFAULT modifiers
Next
From: "Kevin Grittner"
Date:
Subject: Re: shared_buffers documentation