Implement error checking for pthreads calls in thread-safe mode. They really
should always succeed, but in the likely event of a failure we would previously fall through *without locking* - the new code will exit(1). Printing the error message on stderr will not work for all applications, but it's better than nothing at all - and our API doesn't provide a way to return the error to the caller.
Showing
- src/interfaces/libpq/fe-connect.c 13 additions, 4 deletionssrc/interfaces/libpq/fe-connect.c
- src/interfaces/libpq/fe-secure.c 22 additions, 6 deletionssrc/interfaces/libpq/fe-secure.c
- src/interfaces/libpq/libpq-int.h 8 additions, 1 deletionsrc/interfaces/libpq/libpq-int.h
- src/interfaces/libpq/pthread-win32.c 13 additions, 6 deletionssrc/interfaces/libpq/pthread-win32.c
Loading
Please register or sign in to comment