Re:

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re:
Date: 2003-07-23 14:23:08
Message-ID: Pine.LNX.4.56.0307231613380.1649@krusty.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Shridhar Daithankar writes:

> On linux and freeBSD, that is not an issue.

FreeBSD has a separate libc_r. I don't think they would bother with that
if there was no significant difference.

> I would really like to know for what platforms, locking mutex while selecting
> from connection list or some such object, is going to be such a great
> performance hit.

The performance hit isn't in the mutexes or specifically here or there.
But when you go into thread-safe/reentrant land, wild and wonderful things
happen, different on each platform. We could work out a specific solution
for each platform that fits well with the local custom and is most
convenient to users. But that is not maintainable. So we need to work
out some kind of generalization that works similarly on most platforms.
I'm still unsure what that should really be, but everything thread-safe by
default probably won't suffice.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

  • Re: at 2003-07-22 15:27:45 from Shridhar Daithankar

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2003-07-23 14:31:58 Re: Criteria for contrib/ versus gborg?
Previous Message snpe 2003-07-23 12:46:13 CVS - /project//cvroot/pgsql-server/ src/bin/scripts/po/#cvs.lock : permission denied