SEO

#1 (**permalink**) 04-11-2008, 06:23 AM

Tom Lane wrote:

>"Magnus Hagander" <mha@sollentuna.net> writes:
>
>
>>Here's another version of this patch ;-) I've based it on your patch, so
>>the changes to ovalue etc should sitill be there.
>>
>>
>
>In the spirit of incremental improvement ... I've taken Magnus' version
>and added the proposed change to re-enable Qingqing's patch by skipping
>WaitForSingleObjectEx altogether in the CHECK_FOR_INTERRUPTS code path.
>I also removed WaitForSingleObjectEx in pgwin32_poll_signals(), which
>AFAICS should be just like CHECK_FOR_INTERRUPTS. I think this is what
>we are proposing to actually apply to 8.1beta4. I can't test it though,
>so please check it over...
>
>
>

This patch passes regression and demonstrates the expected speedup on my
machine.

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

#2 (**permalink**) 04-11-2008, 06:23 AM

"Andrew Dunstan" <andrew@dunslane.net> wrote
>
> This patch passes regression and demonstrates the expected speedup on my
> machine.
>

Looks good from here:
- several rounds of regression test
- psql -f set_time_out.sql
- pg_ctl signal sending test
- psql deadlock test

Is there any way to test socket?

Regards,
Qingqing

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance