Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- From: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
- To: Magnus Hagander <mha(at)sollentuna(dot)net>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Date: Mon, 24 Oct 2005 15:27:00 -0400 (EDT)
- Message-id: <Pine(dot)LNX(dot)4(dot)58(dot)0510241511280(dot)15987(at)eon(dot)cs>
On Mon, 24 Oct 2005, Magnus Hagander wrote: > > 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. > Ok. - Test recv() path by runing a psql with "-f time_out.sql" and a batch file executing "pg_ctl kill HUP/USR1" repeatedly. - Test select() path by running two batch files, one is doing "psql -c "set statement_timeout=10" test", the other is doing "pg_ctl kill HUP <postmaster>". Regards, Qingqing
- References:
- Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- From: Magnus Hagander
- Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Prev by Date: Re: [GENERAL] 'a' == 'a '
- Next by Date: Re: Creating table in different database
- Previous by thread: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Next by thread: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Indexes: