X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [64.117.224.193])
	by svr1.postgresql.org (Postfix) with ESMTP id E94AF310128
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Fri, 27 Jun 2003 02:31:40 +0000 (GMT)
Received: from svr1.postgresql.org ([64.117.224.193])
	by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new,
	port 10024) with ESMTP id 60256-07
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Thu, 26 Jun 2003 23:31:30 -0300 (ADT)
Received: from cpc-gw2.cpc.net.au (unknown [210.9.248.93])
	by svr1.postgresql.org (Postfix) with ESMTP id 2C904310135
	for <pgsql-hackers@postgresql.org>;
	Thu, 26 Jun 2003 23:31:29 -0300 (ADT)
Received: from utiba.com
	by Utiba Mail Gateway (2.2.2) with ESMTP id h5R2VT832298;
	Fri, 27 Jun 2003 12:31:29 +1000
Received: from pc37.cpc.net.au (pc37.cpc.net.au [192.168.0.37])
	by Utiba Mail Thingy (0.0.2) with ESMTP id h5R2VQx32067;
	Fri, 27 Jun 2003 12:31:26 +1000
Content-Type: text/plain;
  charset="iso-8859-1"
From: Philip Yarra <philip@utiba.com>
Organization: Utiba
To: Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: ECPG thread success (kind of) on Linux
Date: Fri, 27 Jun 2003 12:31:24 +1000
User-Agent: KMail/1.4.3
Cc: AgentM <agentm@cmu.edu>, pgsql-hackers@postgresql.org
References: <200306270216.h5R2GbK29325@candle.pha.pa.us>
In-Reply-To: <200306270216.h5R2GbK29325@candle.pha.pa.us>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200306271231.24667.philip@utiba.com>
X-Archive-Number: 200306/1122
X-Sequence-Number: 40429

On Fri, 27 Jun 2003 12:16 pm, Bruce Momjian wrote:
> BSD/OS supports:
>
> 	The pthreads library conforms to IEEE Std1003.1c
> 	(``POSIX'').
>
> How is that different from UNIX98?

Just checked up on this: apparently version "g" of the standard does contai=
n=20
such manipulation functions... and Tru64's man page for=20=20
pthread_mutexattr_settype claims:

Interfaces documented on this reference page conform to industry standards
  as follows:

  IEEE Std 1003.1c-1995, POSIX System Application Program Interface

Of course, they might be lying.

Anyway, hopefully I can just avoid these recursive locks, and avoid finding=
=20
out who supports what.=20

Regards, Philip.