pgsql: Use CRITICAL_SECTION instead of Mutexes for thread-locking in

From: mha(at)postgresql(dot)org (Magnus Hagander)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use CRITICAL_SECTION instead of Mutexes for thread-locking in
Date: 2008-05-21 14:20:48
Message-ID: 20080521142048.88596754C54@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Use CRITICAL_SECTION instead of Mutexes for thread-locking in libpq on
Windows, for better performance.

Per suggestion from Andrew Chernow, but not his patch since the underlying
code was changed to deal with return values.

Modified Files:
--------------
pgsql/src/interfaces/libpq:
pthread-win32.c (r1.16 -> r1.17)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/pthread-win32.c?r1=1.16&r2=1.17)
pgsql/src/port:
pthread-win32.h (r1.4 -> r1.5)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/port/pthread-win32.h?r1=1.4&r2=1.5)

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2008-05-21 16:00:10 pgsql: Fix function headers not matching prototype in header file, per
Previous Message User Okbob 2008-05-21 10:36:07 orafce - orafce: regress tests for plunit some small fix ToDo: README