Re: [HACKERS] pthread portability

2016-03-29 Thread Michael McConville
Alvaro Herrera wrote: > Michael McConville wrote: > > The below diff fixes one problem: you can't compare pthread_t values > > directly. Only the function pthread_equal(3) is defined. Direct > > comparison usually works because most implementations define > > pthread_t as an integer type. > > So i

Re: [HACKERS] pthread portability

2016-03-29 Thread Tom Lane
Christoph Moench-Tegeder writes: > ## Alvaro Herrera (alvhe...@2ndquadrant.com): >>> The below diff fixes one problem: you can't compare pthread_t values >>> directly. Only the function pthread_equal(3) is defined. Direct >>> comparison usually works because most implementations define pthread_t >

Re: [HACKERS] pthread portability

2016-03-29 Thread Christoph Moench-Tegeder
## Alvaro Herrera (alvhe...@2ndquadrant.com): > > The below diff fixes one problem: you can't compare pthread_t values > > directly. Only the function pthread_equal(3) is defined. Direct > > comparison usually works because most implementations define pthread_t > > as an integer type. > > So is t

Re: [HACKERS] pthread portability

2016-03-28 Thread Alvaro Herrera
Michael McConville wrote: > The below diff fixes one problem: you can't compare pthread_t values > directly. Only the function pthread_equal(3) is defined. Direct > comparison usually works because most implementations define pthread_t > as an integer type. So is there a platform where this assump