Magnus Hagander wrote:
> The other way to go is to try to make the signal handlers thread safe.
> Do you know offhand how much code they touch? Since they're not called
> often, one could perhaps start with just wrapping all the code they
> touch (and that touches the same data they do) in critical sections.
> They're very lightweight and shouldn't have a noticeable performance
> impact, if it's possible to identify a limited number of locations to
> put it in there (as we certainly wouldn't want to bloat the code all
> over the place)
Don't forget that you have to add the volatile modifier to keep the
compiler from optimizing flags outside of loops, etc. for variables
that could change inside a critical section.
pgsql-hackers-win32 by date
|Next:||From: Zeugswetter Andreas SB SD||Date: 2003-12-18 18:09:53|
|Subject: Re: [HACKERS] [PATCHES] fork/exec patch|
|Previous:||From: Magnus Hagander||Date: 2003-12-17 18:08:50|
|Subject: Re: [HACKERS] [PATCHES] fork/exec patch |