Larry Rosenman <[EMAIL PROTECTED]> writes: >> We've called that routine s_lock for a *long* time, so it seems >> like there must be some factor involved that I don't see just yet... > Didn't your commit message say something about the TAS and NON-TAS > paths being the same now? Yeah, but don't tell me you were running on a non-TAS platform... that stuff didn't work... regards, tom lane
- [HACKERS] LOCK Fixes/Break on FreeBSD 4.2-STABLE Larry Rosenman
- Re: [HACKERS] LOCK Fixes/Break on FreeBSD 4.2-STABLE Larry Rosenman
- [HACKERS] Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE Tom Lane
- [HACKERS] Re: LOCK Fixes/Break on FreeBSD 4.2-ST... Larry Rosenman
- [HACKERS] Re: LOCK Fixes/Break on FreeBSD 4.... Larry Rosenman
- [HACKERS] Re: LOCK Fixes/Break on FreeBS... Tom Lane
- [HACKERS] Re: LOCK Fixes/Break on F... Larry Rosenman
- Re: [HACKERS] Re: LOCK Fixes/Br... Tom Lane
- Re: [HACKERS] Re: LOCK Fixe... Larry Rosenman
- Re: [HACKERS] Re: LOCK Fixe... Larry Rosenman
- Re: [HACKERS] Re: LOCK Fixe... Larry Rosenman
- [HACKERS] Re: LOCK Fixes/Break on FreeBSD 4.2-ST... Larry Rosenman
- Re: [HACKERS] Re: LOCK Fixes/Break on FreeBS... Alfred Perlstein
- Re: [HACKERS] Re: LOCK Fixes/Break on Fr... Larry Rosenman
- Re: [HACKERS] Re: LOCK Fixes/Break ... Alfred Perlstein
- Re: [HACKERS] Re: LOCK Fixes/Br... Larry Rosenman
- Re: [HACKERS] Re: LOCK Fixes/Break on FreeBS... Alfred Perlstein
- Re: [HACKERS] Re: LOCK Fixes/Break on Fr... Larry Rosenman