Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKnAB-0005E2-Tp for pgsql-hackers@arkaria.postgresql.org; Sun, 28 Apr 2019 17:00:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hKnAA-0001SS-5b for pgsql-hackers@arkaria.postgresql.org; Sun, 28 Apr 2019 17:00:26 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKnA9-0001PK-JF for pgsql-hackers@lists.postgresql.org; Sun, 28 Apr 2019 17:00:25 +0000 Received: from mail-pl1-x643.google.com ([2607:f8b0:4864:20::643]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKnA2-0005Iq-1c for pgsql-hackers@postgresql.org; Sun, 28 Apr 2019 17:00:24 +0000 Received: by mail-pl1-x643.google.com with SMTP id o5so3940252pls.12 for ; Sun, 28 Apr 2019 10:00:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ilaWhgDTE/RgmM30mUk0//vSMLee8c0klOPriYipVko=; b=AjjdOtlXqgVHlfwK88u1l+Cs2uLvyNJMHM3NkoRbVPgNhCm7kCxs1lcxPLRpTgTbic cU++i9YVk0GG+64xAxbYsUirlNKxhZsyumgzznTTwfcLPqlBbYf5VTIKivbDmDuOqGV3 zsv4lLfZsnLbek0Coggck+YE+ymdaWBSfTTZg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ilaWhgDTE/RgmM30mUk0//vSMLee8c0klOPriYipVko=; b=lcoMd8tYlh6PQhwgEQADxQDx7VZryC2OA9fCKBpYHuisqelbTEfOREJ1ptUOGLbBc9 3s5WOIn1OEAy51XSXUVtliowSWU5QP7ra7w9w2v1NdQ4IvyX31+1mt9iaT+mOxbO8Tya sa20QLa5V+60Elm2fzqlQIZKbiWy4qei1v6JLOUPGBHFlaTpTtRnE27sfaeOJ6YEpiWd OQAnJHUdD9pSrw8MpBtToDRkXhOkUSLO9uaGpqp08WHqO9hlrj9QEZzAkfLEZCu1P45d 3z5KfCMB9m6ZNCVsl5WsO/0dvHdn/iYRluXxydpZ3z8mFaXP8jf1I4PMZmGtQWJS2+qH Xa8w== X-Gm-Message-State: APjAAAXzqcjcTsCaO5kJE2VrAvHCSyzVASUioA/ZTedMjyH/gr9s7WEb W4H21p/GNpzY4zsEZ+8ZnX6CVg== X-Google-Smtp-Source: APXvYqzbXVsLZdrsuxgUHwkabO1pAS1eOchceh2z+u0bJH+qlw8P5IvBU/ukYE7eUyQHqwtSLv5IHw== X-Received: by 2002:a17:902:8a95:: with SMTP id p21mr11724953plo.126.1556470814640; Sun, 28 Apr 2019 10:00:14 -0700 (PDT) Received: from rfd.leadboat.com (108-233-125-46.lightspeed.sntcca.sbcglobal.net. [108.233.125.46]) by smtp.gmail.com with ESMTPSA id k7sm4174179pfk.93.2019.04.28.10.00.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Apr 2019 10:00:13 -0700 (PDT) Date: Sun, 28 Apr 2019 10:00:11 -0700 From: Noah Misch To: Daniel Gustafsson Cc: Kyotaro HORIGUCHI , "9erthalion6@gmail.com" <9erthalion6@gmail.com>, "sfrost@snowman.net" , "pgsql-hackers@postgresql.org" Subject: Re: [HACKERS] Weaker shmem interlock w/o postmaster.pid Message-ID: <20190428170011.GC200983@rfd.leadboat.com> References: <20181130065140.GB2774301@rfd.leadboat.com> <20181203004106.GA2860387@rfd.leadboat.com> <20190304.180420.139624607.horiguchi.kyotaro@lab.ntt.co.jp> <20190307032422.GB1797215@rfd.leadboat.com> <20190309071610.GA2039121@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Mar 29, 2019 at 09:53:51AM +0000, Daniel Gustafsson wrote: > On Saturday, March 9, 2019 8:16 AM, Noah Misch wrote: > > I tested on Red Hat and on Windows Server 2016; I won't be shocked > > if the test (not the code under test) breaks on other Windows configurations. > > IIRC there are Windows versions where Win32::Process::KillProcess is required > for this, but thats admittedly somewhat dated knowledge. If the buildfarm goes > red on older Windows animals it might be something to look at perhaps. Since my second attempt at committing this (commit c098509), I fixed these bugs in the new test file: - MSYS-orchestrated mingw32 (buildfarm member jacana) failed the Perl kill(9, ...) calls[1]. For HEAD and v11, using "pg_ctl kill KILL " fixed that. For v10 and v9.6, I disabled the test under msys. I can reproduce this with Perl 5.28 from msys2. Its kill(9, ...) fails for any non-msys2 process (any ordinary Windows process). [commits 947a350, 2bc0474] - The regress.dll path needed MSYS-to-w32 path translation. [commit 9daefff] - The changes to port selection in get_new_node() made Linux-specific assumptions, so Windows builds had much less protection against port conflict. [commit 4ab02e8] - Got EPIPE when writing to stdin of a child process that exited too quickly. [commit e12a472] Things have been stable on the buildfarm for the last twelve days, so I think this one is over. [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jacana&dt=2019-04-13%2014%3A39%3A17