[HACKERS] ECPG - Specifying connections, TSD, sqlca.

2004-03-09 Thread Lee Kindness
Shridhar, Once the patches I've put forward are applied there's still a further change I've got planned which will remove the mutex locking in the common case - a NULL/DEFAULT connection parameter (I'll post a patch soon). This leaves the threaded case with comparable performance to the

Re: [HACKERS] ECPG - Specifying connections, TSD, sqlca.

2004-03-09 Thread Bruce Momjian
Lee Kindness wrote: Shridhar, Once the patches I've put forward are applied there's still a further change I've got planned which will remove the mutex locking in the common case - a NULL/DEFAULT connection parameter (I'll post a patch soon). This leaves the threaded case with comparable

Re: [HACKERS] ECPG - Specifying connections, TSD, sqlca.

2004-03-09 Thread Bruce Momjian
Lee Kindness wrote: From: Bruce Momjian [EMAIL PROTECTED] Lee Kindness wrote: I still think it's worthwhile investigating the use of GCC's __thread storage class specifier to remove the use of pthread_*specific in this case. This would also be a help to the WIN32 port since this

Re: [HACKERS] ECPG - Specifying connections, TSD, sqlca.

2004-03-09 Thread Lee Kindness
From: Bruce Momjian [EMAIL PROTECTED] Lee Kindness wrote: I still think it's worthwhile investigating the use of GCC's __thread storage class specifier to remove the use of pthread_*specific in this case. This would also be a help to the WIN32 port since this specifier maps well to

Re: [HACKERS] ECPG - Specifying connections, TSD, sqlca.

2004-03-09 Thread Lee Kindness
From: Bruce Momjian [EMAIL PROTECTED] Lee Kindness wrote: Perhaps a cleaner way is to use an existing thread package with encompasses the various platform APIs - i.e. APR or ACE, or... But that's a big discussion, and not one I'm keen to get into at the moment. A more appropriate time is