Skip site navigation (1) Skip section navigation (2)

Re: Win32 semaphore patch

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: Win32 semaphore patch
Date: 2006-04-20 13:37:11
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA352D3@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-patches
In PGSemaphoreLock, should't ImmediateInterruptOK be reset in all cases?
It's not reset if we get the semaphore now. Though I won't claim to
entirely know what that flag does ;-)

(btw, I got double newlines all over)

//Magnus 

> -----Original Message-----
> From: pgsql-patches-owner(at)postgresql(dot)org 
> [mailto:pgsql-patches-owner(at)postgresql(dot)org] On Behalf Of Qingqing Zhou
> Sent: Thursday, April 20, 2006 2:06 PM
> To: pgsql-patches(at)postgresql(dot)org
> Subject: [PATCHES] Win32 semaphore patch 
> 
> Attached is a patch for Win32 semaphore reimplementation per 
> discussion with Tom and Magnus. Basically it implements the 
> interfaces defined in pg_sema.h using unnamed semaphores in 
> Win32. Change in configure.in is needed to support this modification.
> 
> Regards,
> Qingqing
> 

pgsql-patches by date

Next:From: Tom LaneDate: 2006-04-20 14:38:36
Subject: Re: BUG #2401: spinlocks not available on amd64
Previous:From: Qingqing ZhouDate: 2006-04-20 12:05:49
Subject: Win32 semaphore patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group