Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cqdp3-0008Vp-Lb for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Mar 2017 10:48:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cqdp3-0000SC-8M for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Mar 2017 10:48:57 +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.84_2) (envelope-from ) id 1cqdp1-0000Lc-5i for pgsql-hackers@postgresql.org; Wed, 22 Mar 2017 10:48:55 +0000 Received: from mail-wr0-x243.google.com ([2a00:1450:400c:c0c::243]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cqdoz-0001ud-1d; Wed, 22 Mar 2017 10:48:54 +0000 Received: by mail-wr0-x243.google.com with SMTP id u108so26175669wrb.2; Wed, 22 Mar 2017 03:48:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=UtBhcHqqFhPbxx0MjJ0Z33V58h/lPjwkDohUMy1Yko8=; b=eu8wz9T3GbjORMj3DFmTWByDyeAWSPIOdVTR1datLqzFhPQobzpLd8KCFTqLjNp58c d2zVXTJm4e1Ijj4/SuNOLuCR6hxaILNI5+P7Rx47t+3TFVWtj6qrxLhtfVKTwbh0hbV3 Z7HsVdcP/nS1vXu3M5xlD3vtKav/1PPaNuiZBDIR1STDgZJbs8lucxu2yCxbLDjDB1qD NPBZq82Zthm3lhYYx5WYtDnL17IBMaJdMCJpkw9pOHWiqhD6XEDudONopHojAES2v4Ea L/ce5UACAVMjxcEu3DI0l00ItCAD9mmPLfik8YKg1+Wn8dFiOSKpxeBl8LnGnzeKzA6I 5B0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=UtBhcHqqFhPbxx0MjJ0Z33V58h/lPjwkDohUMy1Yko8=; b=Ag3s5QuRp9Ka6SFsBMqLEYRuTNAm1J18OMwd/76uGrGdVl/AuunAvO+NMsS8JHw/Wa kyoUAdr6cQDMIs79Sec0PAeoWMKC2pEcwGMtyZUKOyeaeAa24Ea5WEMzVPcJ7nZqxxZf lkni0Ser+8pnqOgUW3XnbWyIt1CfLkGzKtMVUyrWUvU/Ql+244b4PTIDL3+GCwHn1JkV chNz6SPKEHzAdmti69G3lwjknntPrGflgmGxDNtDtb07hZNosflq01JR3ddE5Elfq0as VS5909HFLIEhK0py72iXI+DQPQSiOCYDJXPSjNf8YABfVkuXtn+zkhzZzWjXWek1BaUC ma9w== X-Gm-Message-State: AFeK/H2KR1eQSm2msBhuAwEtYslnE44YubbPsFp3FdCL6UcMi9ZCDPuReRqbW7vxXzMclA== X-Received: by 10.223.142.136 with SMTP id q8mr2369452wrb.25.1490179732183; Wed, 22 Mar 2017 03:48:52 -0700 (PDT) Received: from [192.168.1.99] (dsl-hkibrasgw1-50df7f-241.dhcp.inet.fi. [80.223.127.241]) by smtp.gmail.com with ESMTPSA id q1sm1330042wra.65.2017.03.22.03.48.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Mar 2017 03:48:51 -0700 (PDT) Subject: Re: [COMMITTERS] pgsql: Fix and simplify check for whether we're running as Windows serv To: Tom Lane References: <16609.1489773427@sss.pgh.pa.us> <2970.1489959622@sss.pgh.pa.us> Cc: Dave Page , pgsql-hackers@postgresql.org From: Heikki Linnakangas Message-ID: Date: Wed, 22 Mar 2017 12:48:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 MIME-Version: 1.0 In-Reply-To: <2970.1489959622@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.7 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 03/19/2017 11:40 PM, Tom Lane wrote: > Heikki Linnakangas writes: >> On 03/17/2017 07:57 PM, Tom Lane wrote: >>> This seems to have broken narwhal: > >> It's not very nice to change the requirements in a minor version, but I >> don't think this would be a real problem for anyone. Not many people >> build PostgreSQL using MinGW, let alone with an ancient version of it. >> But if people don't agree, we could instead revert this patch and apply >> the smaller V2 patch [2] instead, in the back-branches. > >> Thoughts? Any objections to requiring a newer version of MinGW? Any >> objections to do so in the next minor release? > > Hm. I'm +1 for doing that in HEAD, but less so for the back branches. > > Can we get some fix on when the functions in question were added > to MinGW? If we knew how new a toolchain we'd be requiring here, > that would help make this decision. I did some archeology, and found CheckTokenMembership() in MinGW's w32api packages version 3.14 (https://sourceforge.net/projects/mingw/files/MinGW/Base/w32api/w32api-3.14/, in include/winbase.h). According to the timestamps on that download page, that was released in 2009. That was the oldest version I could find, so it might go even further back. Dave, do you know exactly what version of MinGW narwhal is running? And how difficult is it to upgrade to something slightly more modern? Ease of upgrade is another good data point on how far we need to support old versions. - Heikki -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers