Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlWQ0-0003U9-Ep for pgsql-committers@arkaria.postgresql.org; Fri, 12 Nov 2021 13:16:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mlWPz-0007wD-Cw for pgsql-committers@arkaria.postgresql.org; Fri, 12 Nov 2021 13:16:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlWPz-0007w4-4f for pgsql-committers@lists.postgresql.org; Fri, 12 Nov 2021 13:16:35 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlWPu-0001gH-Hc for pgsql-committers@lists.postgresql.org; Fri, 12 Nov 2021 13:16:34 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 50A2F32009F8; Fri, 12 Nov 2021 08:16:28 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 12 Nov 2021 08:16:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=JcAQsN2QFHDlcmqApF17S4t5GZdaoVWOG5IKXLtO3 I4=; b=CxkteIWMQuGS3Fap3xyuvU5onMYdgTJCE+YWvuLM2jF8ViP1wbkPicQX4 WvHQc9LSpkT42aQnw1vYI1/A+jootRqnZS0RmEfhpV86JqyernaN/KBZiNl42eXw BT9096NcugeUqeirJzdmHhLEsRZrC+tIgRkqTrBk53NtKuvAI/2ckv3ABcogrOKC F2ZyLbyOTo9h7qTNqVauLMd4jDkNxNshEczrkbp8evTN9h02smAU2nUuqaq9FSMg hI2J0i07PIpFNDdqvw3mwajKPrSQ7GyZSwGgoDEAlt2z8HqoMSnTQkfTidzgZOQc qx/cNU2NKfg9myLxHQUskaUfSnDbQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrvdefgdegjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejre dttdefjeenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdr vghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomheqnecuggftrfgrth htvghrnhepfeejgeehteeuhfevveduleeufedtjeetiefftedvudfhtdeifefgueettdev gefgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepph gvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 12 Nov 2021 08:16:26 -0500 (EST) Message-ID: <3863895c-d40b-4154-de8f-4961386b2515@enterprisedb.com> Date: Fri, 12 Nov 2021 14:16:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 Subject: Re: pgsql: Remove check for accept() argument types Content-Language: en-US To: Tom Lane Cc: pgsql-committers@lists.postgresql.org References: <1440792.1636558888@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <1440792.1636558888@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10.11.21 16:41, Tom Lane wrote: > Peter Eisentraut writes: >> Remove check for accept() argument types > > Early returns from the buildfarm are > > gaur | 2021-11-09 16:55:58 | auth.c:3235:17: warning: pointer targets in passing argument 6 of 'recvfrom' differ in signedness > gaur | 2021-11-09 16:55:58 | pqcomm.c:722:9: warning: pointer targets in passing argument 3 of 'accept' differ in signedness > gaur | 2021-11-09 16:55:58 | pqcomm.c:743:6: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness > gaur | 2021-11-09 16:55:58 | pgstat.c:483:39: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness > gaur | 2021-11-09 16:55:58 | pgstat.c:630:9: warning: pointer targets in passing argument 5 of 'getsockopt' differ in signedness > gaur | 2021-11-09 16:55:58 | fe-connect.c:2760:11: warning: pointer targets in passing argument 5 of 'getsockopt' differ in signedness > gaur | 2021-11-09 16:55:58 | fe-connect.c:2788:9: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness > > Right offhand I don't see any other animals complaining. > May I suggest that "unsigned int" would be a better choice > than "int" for socklen_t? I have been waiting for a few more buildfarm members to finish (mainly the other AIX and HPUX instances), but they appear to be on strike right now. But based on existing results and extrapolation, it might be that gaur is actually the only one without socklen_t, so we can do whatever we want to make it happy. What does the man page say the correct type would be? size_t?