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 1hGCIx-0001tq-BA for pgsql-committers@arkaria.postgresql.org; Tue, 16 Apr 2019 00:50:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hGCIu-0004OU-EH for pgsql-committers@arkaria.postgresql.org; Tue, 16 Apr 2019 00:50:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hGCIt-0004MX-Rx for pgsql-committers@lists.postgresql.org; Tue, 16 Apr 2019 00:50:28 +0000 Received: from mail-pg1-x542.google.com ([2607:f8b0:4864:20::542]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hGCIq-0004pK-A6 for pgsql-committers@lists.postgresql.org; Tue, 16 Apr 2019 00:50:26 +0000 Received: by mail-pg1-x542.google.com with SMTP id v12so9440103pgq.1 for ; Mon, 15 Apr 2019 17:50:23 -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=+1V1aScNnV3w8Xax5uU9IOSe8uVd8fnnj02+6ksWjck=; b=UX3K2vHBD9nsTukDCXwWNzIYavO8NVwTimRTiaPcv9lihVBmI90eRs+5x3DCsKEZGm hoi8Q7fZy6GqBGHmouHyaK3GUw6BF3P3yy5AbGIa5m2I3SmsorJG9S8Giy3Z1K3CBjoc 2/sS6bfTsu+8u5ZH6Yn3Pl6/KB7bzCpMu0D/k= 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=+1V1aScNnV3w8Xax5uU9IOSe8uVd8fnnj02+6ksWjck=; b=EvBYsQ+vVJSNi4RIM00iAYw2szeZ7tfU0cyW9C/0xRImqLM6QZN/CGm0tdBtlouiLu DbNzv5qh5hzvVZV9FcSHkGj3fIRWcvClhxTxs4jdWcLVc0FXIAKUAY+Xos/2q0HP1I8h EOsWNQB7VqvTG1LGEsuIBn+Qh9IVWvW6go4pB8DzMetcYPAAzE3VSvt3K2JpT2S8vYQs CAsHl3L2xRcK2LicDVavAYDNY5DJ3vjNxrfQW1Y4GEj+uBHJg4KZ9LyOwUPrStwthSnM TUwj7UtGTJ7IgvmhF8QYdih24qQXR6QtAGxNJEQKjgHeLXUiOijoK/31uylGNevlEolA MY3Q== X-Gm-Message-State: APjAAAWMlgXoltbOp8HuYhnISP4++0pxXqhFDGwIG3RNfoiDcf5kphJH +gv3AZHuUxlY3K0+b/COIy1u0MrDLRqRjw== X-Google-Smtp-Source: APXvYqywg7vHfttwt/uqOAvTCGWVy2vQG9YHyZA7UnZfbnh46N2363DyoUJabrgSdkAHBitU6xpXSg== X-Received: by 2002:a63:8848:: with SMTP id l69mr69034148pgd.137.1555375822323; Mon, 15 Apr 2019 17:50:22 -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 h4sm65371895pfo.119.2019.04.15.17.50.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Apr 2019 17:50:21 -0700 (PDT) Date: Mon, 15 Apr 2019 17:50:19 -0700 From: Noah Misch To: Tom Lane Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Consistently test for in-use shared memory. Message-ID: <20190416005019.GA3296237@rfd.leadboat.com> References: <26478.1555373328@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26478.1555373328@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Apr 15, 2019 at 08:08:48PM -0400, Tom Lane wrote: > Noah Misch writes: > > Consistently test for in-use shared memory. > > Hmm ... conchuela has just found another problem with this test case: > > ok 2 - detected live backend via shared memory > # Running: postgres --single -D /home/pgbf/buildroot/HEAD/pgsql.build/src/test/recovery/tmp_check/t_017_shm_gnat_data/pgdata template1 > ack Broken pipe: write( 16, 'SELECT 1 + 1' ) at /usr/local/lib/perl5/site_perl/IPC/Run/IO.pm line 549. > > I interpret this as "the single-user backend exited before we could stuff > 'SELECT 1 + 1' down the pipe to it, and the Perl script is not expecting > to get a write failure there". Perhaps I should write the 'SELECT 1 + 1' to a regular file and redirect input from that file.