I wrote:
> Awhile back, Chris Marcellino <[EMAIL PROTECTED]> wrote:
>> If this is in fact the case, I have a trivial patch to conditionally
>> enable SysV semaphores based on the OS release:
> I've tried this patch on my Mac laptop, and while it seems to work as
> advertised in terms of not eati
Awhile back, Chris Marcellino <[EMAIL PROTECTED]> wrote:
> I searched through the archives and I can't find a mention of why the
> posix_sema code was written for Darwin.
> I assume it is because before Darwin 6.0/Mac OS X 10.2 there was not
> kernel support for SysV semaphores.
> If this is in
From: "Tom Lane" <[EMAIL PROTECTED]>
> Probably not. The issues about Darwin's POSIX-sema implementation
> are (a) eating backend open-file slots, which won't matter when a
> backend only touches a few different tables as pgbench does; and
> (b) extra process-launch overhead, which won't matter to
Chris Marcellino <[EMAIL PROTECTED]> writes:
> On Feb 7, 2007, at 4:54 PM, Tom Lane wrote:
>> Outta curiosity, can you measure any performance difference?
> Using pgbench, on 1 million records at each of 1, 10 and 100
> concurrent users, I get the same results before and after the patch.
> I'm
Using pgbench, on 1 million records at each of 1, 10 and 100
concurrent users, I get the same results before and after the patch.
I'm not sure if pgbench is the most appropriate benchmark for this
though.
The upside to using the SysV sema code on Darwin, to my
understanding, is that the Sys
ostgreSQL is easy!"
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Chris Marcellino" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, February 08, 2007 9:54 AM
Subject: Re: [PATCHES] Configure template change to use SysV Semaphors
on darwin
&g
Chris Marcellino <[EMAIL PROTECTED]> writes:
> I searched through the archives and I can't find a mention of why the
> posix_sema code was written for Darwin.
Because Darwin didn't have anything else at the time.
> If this is in fact the case, I have a trivial patch to conditionally
> enable
