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 1mwwx8-0001sI-Ux for pgsql-committers@arkaria.postgresql.org; Tue, 14 Dec 2021 01:50:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mwwx7-0007rA-32 for pgsql-committers@arkaria.postgresql.org; Tue, 14 Dec 2021 01:50:01 +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 1mwwx5-0007r0-3n for pgsql-committers@lists.postgresql.org; Tue, 14 Dec 2021 01:50:00 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mwwx0-0005Di-9J for pgsql-committers@lists.postgresql.org; Tue, 14 Dec 2021 01:49:58 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 044B85C0308; Mon, 13 Dec 2021 20:49:51 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 13 Dec 2021 20:49:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=rVhESl17S7NX2xl0uk89g7hPKP0 3gJKbzd97J+YeWhM=; b=xwLiBne4wgnTaSI0nKDrJLKu1MLwVG/Wxg2+dbopl8q XN8F6Onoe1Mye/ewTMv4456KLYJX0Ry2Alnnj9uI55Z/5x6rgxi1LgItLubXq/yg afmWti1qHW2ABb0MFnmplS2CHAXSPV+NP0V92DE/h71leLBZ92SrBHSCH5KQJpGh 9s30yyy4+DS4Da9aB+NoHMvNhOnesU2zJV9jLIP0nUGOgUiTJL78nN25Ep/efbBt a2FZRA99SSUWRDeEm2paS+jY5ipK+YZvwwFu82CStDg8uHIkOY5hKddChgTTir9p D3cFkGMZdwq7WgHObvZvd1PuzoX6UkjBTqTucKMhRRw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rVhESl 17S7NX2xl0uk89g7hPKP03gJKbzd97J+YeWhM=; b=lAsE+V97vznNlPFedU2h1x hn6AfG188zFoRrdzjkPTFdQLC0PPhxcBFbaH3775vo020m7Duns4EeKKPH+dxKkW 96FXQOFT+5dA155kSE7NDg3rDyYJWfUDDudexAinNy5DJMAErrDULApYZq9N/c0c mDVe3w92zWK3gHBTE16cflUy1XT0E3zxnsZMmeY6Wux8nQgrHuW4/Rku3O1GrjUV 6PU1D+NhEPWF2iQvHViOxlxlUts7H1Zsa548UstZv0dEFJFZJo02P9IaWrekdeFT 2BxOK6Ig2u8GPXf1OLfniEVQyytIVtT3c3If1c38J3F3V7kV73Shf2Vvg/mqMmOg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrkeelgdegtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculddugedmnecujfgurhepfffhvffukfhfgggtuggjsehttdertddttddv necuhfhrohhmpeetnhgurhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgrii gvlhdruggvqeenucggtffrrghtthgvrhhnpeeikeelueetveetjeeujefgkeetffdtleeh gfffieelvefgveefgeevgedtveejgeenucffohhmrghinhepphhoshhtghhrrdgvshdpph hoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 13 Dec 2021 20:49:50 -0500 (EST) Date: Mon, 13 Dec 2021 17:49:49 -0800 From: Andres Freund To: pgsql-committers@lists.postgresql.org, Thomas Munro Subject: Re: pgsql: isolationtester: append session name to application_name. Message-ID: <20211214014949.o26doqta3cqolz3i@alap3.anarazel.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2021-12-13 20:06:10 +0000, Andres Freund wrote: > isolationtester: append session name to application_name. > > When writing / debugging an isolation test it sometimes is useful to see which > session holds what lock etc. To make it easier, both as part of spec files and > interactively, append the session name to application_name. Since b1907d688 > application_name already contains the test name, this appends the session's > name to that. > > insert-conflict-specconflict did something like this manually, which can now > be removed. > > As we have done lately with other test infrastructure improvements, backpatch > this change, to make it easier to backpatch tests. > > Author: Andres Freund > Reviewed-By: Michael Paquier > Reviewed-By: Andrew Dunstan > Discussion: https://postgr.es/m/20211211012052.2blmzcmxnxqawd2z@alap3.anarazel.de > Backpatch: 10-, to make backpatching of tests easier. Eeelpout failed 020_archive_status.pl with error running SQL: 'psql::1: ERROR: checkpoint request failed https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=eelpout&dt=021-12-13%2020%3A16%3A06 after this and the preceding commit. As neither of two commits since the last successful run touched anything relevant to tap tests or checkpoints I'm assuming it's just chance that eelput failed right now. Greetings, Andres Freund