Andrew Chernow wrote: > I noticed several months ago, and came across it again today, that > libpq's pthread-win32.c implementation is using CreateMutex rather > than CRITICAL_SECTION. CreateMutex is like a semaphore in that it is > designed to be accessible via name system-wide. Even when you don't > give it a name, thus bound to process that created it, it still > carries significant overhead compared to using win32 > CRITICAL_SECTIONs. > > The attached patch replaces the win32 mutex calls with critical > section calls. The change will not affect the behavior of the > windows pthread_xxx functions.
First of all, I like this in general :-) But a couple of comments. It changes the behavior when the pointer passed in is invalid from crash to silent working, right? This shouldn't actually matter, since these functions are only ever supposed to run from callers *inside libpq*, so it probalby doesn't matter... Which brings up the second point - is there any actual reason for adding the pthread_mutex_destroy call? Since libpq never calls it, and it's never used from outside libpq (it's not exported outside the library even), isn't it just going to end up as dead code? //Magnus -- Sent via pgsql-patches mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches