Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g1u6b-00026P-Us for pgsql-committers@arkaria.postgresql.org; Mon, 17 Sep 2018 14:02:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g1u6Z-0002tL-Q3 for pgsql-committers@arkaria.postgresql.org; Mon, 17 Sep 2018 14:02:23 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g1u6X-0002tC-Or for pgsql-committers@lists.postgresql.org; Mon, 17 Sep 2018 14:02:23 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g1u6L-0004Wi-Fi for pgsql-committers@lists.postgresql.org; Mon, 17 Sep 2018 14:02:20 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B32D521DF0; Mon, 17 Sep 2018 10:02:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 17 Sep 2018 10:02:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=FXoFPny9EuWPoFg2QvKCFyYpe459RZ+p4eYhd+WoOzs=; b=lRXL/qob lw+8E0dBdSOb4X7FjaG8cEf0eJPJrDR22IUziJcFnk9yLNwUgcpVItrj+h45lqTX ngxvXISzgKK0cMyCVuDSAdIJixnm0eS74Qb9utYr08G5+8agFab7Izdsq0dHK0Cc KBvWT186e6FRk9EHxQC/fA4uRKIuEK9vi6nogmUN/XSk2PWhrv6/UmnoEYCoH2w2 W2hBHYjslAAyuhvZ1iOXKQm7KNHd/qF2xGUdKbt3X6yJtdM2Snlp0qYZWDU1nAz3 bya8ag59RGgz+UWb0F2OYtEzZ6YNzqZqlbYWBURsruzwsApHyH1MaUNgUuASqBxS laAGya9V/5aCeA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=FXoFPny9EuWPoFg2QvKCFyYpe459R Z+p4eYhd+WoOzs=; b=GBGNcnopqDYPVrctQOC5yKnlCDoFmV+hYg7u2ACKFGBLA 3F0nsBySj+VgEyokMH/a7FPmTM/rZCtrjzgUz4/NWvQ2DYOkri5bvD6fjfZ26YT6 iLiO8peRs64R61/4bnWyUQBEKPjiLrdE+EOcpRchlDpGdYa1XbJESvmKDAL4vihi 9zXoOii+bWLZ2uF6VPFe6ySyZ1LWdEGeCcAoL6B6xYfXIcQ41DZ0Al9CJpu9L/U5 O+aJSc1PSfhxb3y5EYaOxnI+0ywbgrTpp8oCw3NWXSgKCBfpKWKP0dsG/FXIul/g 6OIm1O2OQjHi/TX2FwgDl/mUL6+6BD8Kl8v8MmK8g== X-ME-Proxy: X-ME-Sender: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id B4FB9E4121; Mon, 17 Sep 2018 10:02:05 -0400 (EDT) Date: Mon, 17 Sep 2018 23:02:02 +0900 From: Michael Paquier To: Tom Lane Cc: pgsql-committers@lists.postgresql.org, Andrew Dunstan Subject: Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi Message-ID: <20180917140202.GF31460@paquier.xyz> References: <23543.1536938575@sss.pgh.pa.us> <20180914224939.GA1178@paquier.xyz> <20180917114113.GA31460@paquier.xyz> <17194.1537191697@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dWYAkE0V1FpFQHQ3" Content-Disposition: inline In-Reply-To: <17194.1537191697@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --dWYAkE0V1FpFQHQ3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2018 at 09:41:37AM -0400, Tom Lane wrote: > BTW, I'm a bit concerned by the fact that bowerbird has failed its > last couple of HEAD runs at the pgbench step. The first such > failure was here: >=20 > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dbowerbird&dt=3D= 2018-09-15%2014%3A19%3A58 >=20 > Looking at the set of commits between the prior run and that one, > it's hard to see anything that could have triggered the test failures > other than this patch --- but I also don't see how this patch would've > blown up pgbench without breaking earlier tests. Ideas? Thanks, I have been looking at the build farm but I missed this one. dory, which uses VS 2015 is not complaining because it does not run bincheck. At quick glance, it seems to be caused by process_file() in pgbench.c which would need to open files in text mode, and the input file parsing fails at the first '\' character found. I'll test that stuff on tomorrow morning manually. -- Michael --dWYAkE0V1FpFQHQ3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlufs9oACgkQnvQgOdby QH3w7Q//W1YqKG5+qJCqTCSmOzZqMCLBxeNeKvfWsFzPvK8PHJzFaQUqirNC4iXv aAIGTEKCFBvX2ocK2A/5s+eFc0LNZ0h5Z9QYsvI65C1wH/dd+q2ESRmVhSZrn4QP RYbxoQdLKuRErE59xnzaB1mCF4qRVeCUp8p1IvwwygCji5WZ1l0ToScDE+FW3QRz DPybqOHy78NtwQDLEkRrSdQ1hI95cm2UR1++0XrpGA2DcWA0E+eX+vRe+cfBbEI/ yAdzms0fGdGwMz26t09+RIzHS0sycRqnrEurSQR8g+DrpMqQ9WRDeJaV8ANVlUqt pfK2BFq4ahMZlLyRhrR0z9w+wLjLLhhBwvoakBuAIacLPGc0rOWxIM/ORfqnp2eL qtQD5zGJYaQ/yUbS4RrFqmBydLyllVU6IVL8S4KmKMc68S7qLA9GCzMXLY53U+Pm EraAbLmhVVpmkTtyquj5pkAfmCc9gZh5VEVl95qRboWGt8bxR3JtAANnQ3hlj6j8 FwHMBeGLB/FePP5hAoG61MqkA6WvIUVKGF9ozYFY76MkzrxW4RXgM8G6P0NYVaR2 SaSFt7+UeD4kNbBTtMJ3vjCrYyZE/bzmZyCOu+B+OiKRUpYPYfTr1PtYNIhPa6Q1 GURylV7Fh0+GZjzu+nuqzbzOaFmBvrQfrYhoS49+GLKWb5SNRX4= =iqy3 -----END PGP SIGNATURE----- --dWYAkE0V1FpFQHQ3--