From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, "'pgsql-patches(at)postgresql(dot)org'" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: fork/exec patch |
Date: | 2003-12-16 14:01:33 |
Message-ID: | 20772.1071583293@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 pgsql-patches |
Neil Conway <neilc(at)samurai(dot)com> writes:
> My next question would have been to ask whether switching to a
> spinlock here will be a performance problem. In looking at the code,
> it seems we only hold the ShmemIndexLock for a long time (hundreds of
> instructions & multiple system calls) while bootstrapping the shmem
> index hash table itself. Otherwise, the lock is acquired and released
> quickly, and even then it is only done during backend initialization,
> so there shouldn't be much contention for it. Is this analysis
> correct?
Yes, at least that was the theory I was working from when I suggested
Claudio do it this way ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-12-16 14:12:16 | Re: 7.4 include file conflict |
Previous Message | Michael Meskes | 2003-12-16 12:18:20 | Re: 7.4 include file conflict |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-12-16 14:23:33 | Re: libpq.dll for win32 always using ssl |
Previous Message | Tony and Bryn Reina | 2003-12-16 12:57:22 | libpq.dll for win32 always using ssl |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-12-16 15:29:36 | Re: YA Doc patch |
Previous Message | Claudio Natoli | 2003-12-16 09:27:56 | Re: fork/exec patch |