Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rkwav-00GaGR-Va for pgsql-committers@arkaria.postgresql.org; Fri, 15 Mar 2024 01:42:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rkwas-004wSp-VO for pgsql-committers@arkaria.postgresql.org; Fri, 15 Mar 2024 01:42:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rkwas-004wSe-Ny for pgsql-committers@lists.postgresql.org; Fri, 15 Mar 2024 01:42:47 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rkwal-004ZZw-U5 for pgsql-committers@lists.postgresql.org; Fri, 15 Mar 2024 01:42:46 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3bbbc6e51d0so1095689b6e.3 for ; Thu, 14 Mar 2024 18:42:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710466958; x=1711071758; darn=lists.postgresql.org; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:from:subject:cc:to:message-id:date:from:to:cc:subject :date:message-id:reply-to; bh=Zh3tDY3AP3TMxsccjqa9PTtFxhsTxglo0fX6XwL7pBA=; b=mM0nycXriOkb+nyX2vUqwYSBskencqycnlM8eOW7IOMHToVtBl6GDja33//5HCoohn vnyac7P75dzYgHZ/p0/R00vsA2sI20zOjZivTMDgpZQvKIcUpddnLHuLyn3hrw/UkYlt Kjnu140SVazenO396fMDSAYYxybJ0i+3wHdwmZo6z7O2S4bwVmpuvuHOGsfq6WiCe7X3 DLNDoMtKnMyedYJH1uowrgyGHCoVZL9kJ4YFigYqWlY2WgkfVtH03BtPxH6O0vRo5xFh Eyn0MbQgTsB63e1lIcZ5qzkTdofmJ4NX7f9z4oqbapSRBOYJdcHXYJnBYukrbOBY7ydp ntZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710466958; x=1711071758; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:from:subject:cc:to:message-id:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Zh3tDY3AP3TMxsccjqa9PTtFxhsTxglo0fX6XwL7pBA=; b=gT5oRTj2K+iW/MOWbe5UD6iQV5VX/nh8XbOJh9RVWIJBOwfWzsYQQwR/CG5V37I0fK 9XYzipCtRw42lUXMqckagOAhxEGToeorHVk+OHBK2RK5PEmDMbvFsKUMfgthWsVHh2at V6NOS254Gi82opqmYVlOw3NKc7a5T4HVZdkTMmzgdJsB/oXa8N414DVTEgerUHdG+j8H wmVfuiYqAKZQxHDV5e8cHMiwnYwtOpdHZd6VkujLncZE7P3SdmmzAHhUc9n4CoifYXO4 ak/Aa+lIf+iCsWsOLBnt22Uu1NNAj2Pnu/Fesf/sLHv5XpHDxxdpUuTasomTKTbqEdGU lFQA== X-Gm-Message-State: AOJu0Yz/EItVgjM/orvgskq+NhhbZZnjAvvsjVYJExVTEAjDifKxcQHD 97BATfLS6DLPKiRepkLWTzlPfMcfOYwqRdndvGbpupRwRdCAuEPT X-Google-Smtp-Source: AGHT+IFCjzQSilPVTwi4MPmvaVR/Uv9vIfFxAJakia6kefdvpsqZ7AGh27Yv66Pxas6mkwPZQTO3wA== X-Received: by 2002:a05:6871:2891:b0:222:570a:72c7 with SMTP id bq17-20020a056871289100b00222570a72c7mr3882900oac.45.1710466957864; Thu, 14 Mar 2024 18:42:37 -0700 (PDT) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id kt2-20020a056a004ba200b006e6233563cesm2177649pfb.218.2024.03.14.18.42.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Mar 2024 18:42:37 -0700 (PDT) Date: Fri, 15 Mar 2024 10:42:35 +0900 (JST) Message-Id: <20240315.104235.1835366724413653745.horikyota.ntt@gmail.com> To: akorotkov@postgresql.org Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Add TAP tests for timeouts From: Kyotaro Horiguchi In-Reply-To: References: User-Agent: Mew version 6.8 on Emacs 27.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello. At Thu, 14 Mar 2024 11:25:42 +0000, Alexander Korotkov wrote in > Add TAP tests for timeouts > > This commit adds new tests to verify that transaction_timeout, > idle_session_timeout, and idle_in_transaction_session_timeout work as expected. > We introduce new injection points in before throwing a timeout FATAL error > and check these injection points are reached. > > Discussion: https://postgr.es/m/CAAhFRxiQsRs2Eq5kCo9nXE3HTugsAAJdSQSmxncivebAxdmBjQ%40mail.gmail.com > Author: Andrey Borodin > Reviewed-by: Alexander Korotkov In 005_timeouts.pl, I found the following comment. > # If we send \q with $psql_session->quit it can get to pump already closed. > # So \q is in initial script, here we only finish IPC::Run. > $psql_session->{run}->finish; I'm not sure if "it can get to pump already closed." makes sense. I guess that it means "the command can get to be pumped (or "can be sent") to the session already closed" or something similar? > # 2. Test of the sidle in transaction timeout s/sidle/idle/ ? > # Wait until the backend is in the timeout injection point. I'm not sure, but it seems that "is in" meant "passes" or something like? regards. -- Kyotaro Horiguchi NTT Open Source Software Center