Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
- To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Date: Mon, 24 Oct 2005 09:47:22 +0200
- Message-id: <6BCB9D8A16AC4241919521715F4D8BCE6C7AF4(at)algol(dot)sollentuna(dot)se>
> > 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?
Send the backend a signal when it's blocking for socket input (waiting
for a user command in a psql session for example), and see that it's
delivered. Hitting hte postmaster will test the select() path, and
hitting a backend will test the recv() path, IIRC.
//Magnus
Home |
Main Index |
Thread Index