Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mgQVs-0001pg-Rx for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Oct 2021 11:57:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mgQVr-00007q-Pw for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Oct 2021 11:57:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mgQVr-00007h-Bl for pgsql-bugs@lists.postgresql.org; Fri, 29 Oct 2021 11:57:35 +0000 Received: from mail-qk1-x72b.google.com ([2607:f8b0:4864:20::72b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mgQVp-00025p-4D for pgsql-bugs@lists.postgresql.org; Fri, 29 Oct 2021 11:57:35 +0000 Received: by mail-qk1-x72b.google.com with SMTP id y10so8957265qkp.9 for ; Fri, 29 Oct 2021 04:57:32 -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=GU3jJq3OlIfa65JJ73tJerw+Z1ZzcSsKOmP+TN8ut7I=; b=GvFDHPCrQQpt55NtNTk+x89cz38LjVlpOCxW8dnXVSgR7PsnuEuUUW89taz7ILseXY uzFoqxmqqoQzDPi7dMf7Z6COuoAiWxgxM/zSiwHiSIyiZKGCPM6b0O1h6ykH3PeE9hTx wJFVC+nbG/5rFCuqIEqyWJcI6V/Snvxj/yOAo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=GU3jJq3OlIfa65JJ73tJerw+Z1ZzcSsKOmP+TN8ut7I=; b=i+L/o0GJ0ya2+MQpHpUaO08UmCMecI8AHI7xkDeJ8WkUsEWfbSx2vgt81ScLGmYJxA +PLT5fimAIobBa2e5Hea5HPcqbQbsOY7tG96jVJu6TQaXowkAtxEicuy1o2igbjBCq4m 1DC0T4AyYykD5icdqmNglMwAmMDIXgSy0dRTBQPnmt4yaK8KYQCwbki3E3eo4x6iw2GS bah7AiMvz+cM23vRcb5UoYqLSfmfKVD0U+UfYlkvIiu0tA3EK+7kXCv+l/BRuQanxGRk jYTw+A7edtjOREFjvB1M8dNQXNEUj9UkJe2oGi0EbfFms6B1+tap0AZvKbvF9UklAUmY YItA== X-Gm-Message-State: AOAM533clYF2SRt/b9ZpxTtUUNdTwrutbCvBK0ZW8buCnZ/VemmYVPi0 1v5N4pcbpJycAoU5zA0PJcb8VQ== X-Google-Smtp-Source: ABdhPJxn7M+u1GS4RnruMX5jMhshdMWXBGpPJKQKswCsfKh1z1Y24uKXMnBwigKMgd2Zgy+jdzCfRw== X-Received: by 2002:a37:2ec6:: with SMTP id u189mr8433582qkh.466.1635508649137; Fri, 29 Oct 2021 04:57:29 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::46]) by smtp.gmail.com with ESMTPSA id a15sm3677693qkp.17.2021.10.29.04.57.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Oct 2021 04:57:28 -0700 (PDT) Date: Fri, 29 Oct 2021 04:57:25 -0700 From: Noah Misch To: Thomas Munro Cc: Tom Lane , Andrey Borodin , PostgreSQL mailing lists , Michael Paquier , Peter Geoghegan , Andres Freund Subject: Re: conchuela timeouts since 2021-10-09 system upgrade Message-ID: <20211029115725.GA309057@rfd.leadboat.com> References: <20211017151205.GA2384251@rfd.leadboat.com> <9BA43784-E4A7-4638-900C-FC9868C388FA@yandex-team.ru> <20211019030212.GB3403374@rfd.leadboat.com> <20211024050028.GA3310519@rfd.leadboat.com> <64835CF9-D9AA-49BF-A685-01C23B1023C1@yandex-team.ru> <20211024161942.GB3945842@rfd.leadboat.com> <640FA6DC-A998-4499-B3B4-2773685B8C56@yandex-team.ru> <20211029025600.GB298507@rfd.leadboat.com> <581193.1635477596@sss.pgh.pa.us> 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: Archived-At: Precedence: bulk On Fri, Oct 29, 2021 at 04:42:31PM +1300, Thomas Munro wrote: > On Fri, Oct 29, 2021 at 4:20 PM Tom Lane wrote: > > It indeed is looking like 7f580aa made the problem go away on conchuela, > > but do we understand why? I don't. > > The only theory I can think of is "kernel bug", > > but while that's plausible for prairiedog it seems hard to credit for a > > late-model BSD kernel. DragonFly BSD is a niche OS, so I'm more willing than usual to conclude that. Could be a bug in IPC::Run or in the port of Perl to DragonFly, but those feel less likely than the kernel. The upgrade from DragonFly v4.4.3 to DragonFly v6.0.0, which introduced this form of PostgreSQL test breakage, also updated Perl from v5.20.3 to 5.32.1. > I have yet to even log into a DBSD system (my attempt to install the > 6.0.1 ISO on bhyve failed for lack of a driver, or something), but I > do intend to get it working at some point. But I can offer a poorly > researched wildly speculative hypothesis: DBSD forked from FBSD in > 2003. macOS 10.3 took FBSD's kqueue code in... 2003. So maybe a bug > was fixed later that they both inherited? Or perhaps that makes no > sense, I dunno. It'd be nice to try to write a repro and send them a > report, if we can. The conchuela bug and the prairiedog bug both present with a timeout in IPC::Run::finish, but the similarity ends there. On prairiedog, the postmaster was stuck when it should have been reading a query from pgbench. On conchuela, pgbench ran to completion and became a zombie, and IPC::Run got stuck when it should have been reaping that zombie. Good thought, however.