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: 2005-10-24 07:47:22
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE6C7AF4@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2005-10-24 08:03:29 Re: Query Progress Estimator
Previous Message Simon Riggs 2005-10-24 07:47:05 Re: On externals sorts and other IO bottlenecks in