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 1g1vDW-0007Kz-8f for pgsql-committers@arkaria.postgresql.org; Mon, 17 Sep 2018 15:13:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g1vDU-0004fo-Du for pgsql-committers@arkaria.postgresql.org; Mon, 17 Sep 2018 15:13:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g1vDU-0004fh-5B for pgsql-committers@lists.postgresql.org; Mon, 17 Sep 2018 15:13:36 +0000 Received: from mail-yw1-xc42.google.com ([2607:f8b0:4864:20::c42]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1g1vDQ-00032s-J9 for pgsql-committers@lists.postgresql.org; Mon, 17 Sep 2018 15:13:35 +0000 Received: by mail-yw1-xc42.google.com with SMTP id 14-v6so5574129ywe.2 for ; Mon, 17 Sep 2018 08:13:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=k4V2NpMbq6qpt8jG1akSMGTM3qiCNvbV1JGIaNzx/xk=; b=C7Z+IJxr5qTvzowCzjZ9X6RG43ueEQKz0Xz9O7u2tylAmepP56QKvwesmpEGAeFwVj jX9glUrenMhpB348zbR99/MGoPewl2WKUB6WMPEMutxIjaiRRjiDvZJtIGSBrJ996gWc AGMVa3HPj/jxFag4cQvHsjRAnibQI4zCvvrlk9nDxttkQjQN2wIv1WKJic8b+1hLbNAz 8t1KtaWYbeF3kr5dV74Zfi8Y6lxkK/Z4I82AaDej+QSkB3Idri3Ob9rzPRVFfrZGtQeh AizBiQ2/+DJ3Sb1XcG4514lmMVVJCRy2mDenAWB+kjn1PrU009SpYUsabmnEB97d6QTh ZkXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=k4V2NpMbq6qpt8jG1akSMGTM3qiCNvbV1JGIaNzx/xk=; b=KlSzRzfRpA4i5Sgv5c8aCHU7n59o+1g8S2zd8wwCakxUh0K21La3SefbjoZ6jssgMj Em1z2wZJfJTYmfxqMAmyMryq6o/QR5Rg4P5KX6nnTXyW6QieRNmutkDLhs6DbHvjTwKx mqeE47kOZDCrNAHw9MGmfxn21f1g7j5GyLbNVXdAuJ5zES45SwNJomtgPHnL3wglCXKE p35oRf7Dwse+MVUY39zTpda+/OPlssy8YJy7LJFlF0JmYyAuIO6VXkXA8nFpX89tHN3q 7tOJvDBTWcA91hLHBYsdIYnGnLkjGac+cbCAUyxTw21JwplEmEsgfO4plcg1sP1Vx3y0 fSOw== X-Gm-Message-State: APzg51C8k0ZZDfdBfm/pu3JfR06a8L0Vyi8UswhvesXII/Mt+boqOIo9 84yCHTI9DLUfT8DWD+/mxcz5+TysVSVsE6xeja/GK/6ZH+PIVCMsUfFrYwf/NHKRPG69rKzvnFS A7O0RXhvSDVZeNY+wn7EcGu9uA853RjHGvd129EgyVOhuIhM9GkrCI9jhcyzbDqR6O1X673465k 5xYCK8DEwp6xjs+9J18ikKlrvu X-Google-Smtp-Source: ANB0VdbUD0ERhzWvY0uGqODEZXVnjnRJNKeBnsQYmjkoQmjYsar5z4naIBWHAflzJ7+JID5BJxSbtw== X-Received: by 2002:a0d:cb88:: with SMTP id n130-v6mr10278705ywd.243.1537197209852; Mon, 17 Sep 2018 08:13:29 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id n6-v6sm6140725ywe.89.2018.09.17.08.13.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Sep 2018 08:13:29 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi To: Tom Lane , Michael Paquier Cc: pgsql-committers@lists.postgresql.org References: <23543.1536938575@sss.pgh.pa.us> <20180914224939.GA1178@paquier.xyz> <20180917114113.GA31460@paquier.xyz> <17194.1537191697@sss.pgh.pa.us> <20180917140202.GF31460@paquier.xyz> <19655.1537195712@sss.pgh.pa.us> Message-ID: Date: Mon, 17 Sep 2018 11:13:28 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <19655.1537195712@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-MW List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 09/17/2018 10:48 AM, Tom Lane wrote: > Michael Paquier writes: >> On Mon, Sep 17, 2018 at 09:41:37AM -0400, Tom Lane wrote: >>> 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. > Oh, you're thinking pgbench isn't robust against finding \r's visible > in its input? Could be. > >> I'll test that stuff on tomorrow morning manually. > We've got a bit of a timing problem because we want to wrap 11beta4/rc1 > (still TBD) in a few hours. I'll take a look and see if I can push a > quick fix before that. When you do I'll start a bowerbird run to check it. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services