pgsql: libpq: use pgsocket for socket values, for portability

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: libpq: use pgsocket for socket values, for portability
Date: 2014-04-16 23:46:56
Message-ID: E1WaZXc-0007Wn-W9@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

libpq: use pgsocket for socket values, for portability

Previously, 'int' was used for socket values in libpq, but socket values
are unsigned on Windows. This is a style correction.

Initial patch and previous PGINVALID_SOCKET initial patch by Joel
Jacobson, modified by me

Report from PVS-Studio

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5d305d86bd917723f09ab4f15c075d90586a210a

Modified Files
--------------
src/interfaces/libpq/fe-connect.c | 34 +++++++++-------------------------
src/interfaces/libpq/fe-exec.c | 2 +-
src/interfaces/libpq/fe-misc.c | 6 +++---
src/interfaces/libpq/fe-protocol2.c | 2 +-
src/interfaces/libpq/fe-protocol3.c | 2 +-
src/interfaces/libpq/libpq-int.h | 2 +-
6 files changed, 16 insertions(+), 32 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2014-04-16 23:53:50 pgsql: docs: properly document psql auto encoding mode
Previous Message Tom Lane 2014-04-16 23:35:58 Re: [COMMITTERS] pgsql: Include planning time in EXPLAIN ANALYZE output.