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 1mxofl-00077L-Fl for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Dec 2021 11:11:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mxofj-0001La-SE for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Dec 2021 11:11:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mxofi-0001LR-T4 for pgsql-hackers@lists.postgresql.org; Thu, 16 Dec 2021 11:11:39 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mxofc-0003I3-Gn for pgsql-hackers@lists.postgresql.org; Thu, 16 Dec 2021 11:11:35 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 5CFC43200E8E; Thu, 16 Dec 2021 06:11:29 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 16 Dec 2021 06:11:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=GLqFqVvbgAXgPfPtAGSHyCWLxSlSIF/aQVXmQmxij TI=; b=hPXpkXmoW4/66tS2Yue6ULbZC8msKBEttTdGnqRnK3z6pznzmVTjr/Don 2lJqNzpIO0nizFBiki6qaq5IpfesyQd48TGwwx7SutOHgsMV4gf6RXQ/zsn1BYrp rpRdl6nGYg8cdGEibanXFNqBmQrO9eyhp3h+7OfMsj1P5wM6ARHc+DdSQh4qDaGV 73hmIBHWC+cwtmDQ5xlatT9sTBBPTp3YbA6CBIS9R6RNMLKtqTQb9Yj/ARfVYQzJ 62zj+C8gKk7d5J/0Daku0U4HXqyl22FQBLFkwUr1x03OyrbR55pccegHk5fR3y2z GJo3dV9IvwfCyqbI9mYoGIflhdeQw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrleeggddviecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 16 Dec 2021 06:11:26 -0500 (EST) Message-ID: Date: Thu, 16 Dec 2021 12:11:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Subject: Re: pg_upgrade should truncate/remove its logs before running Content-Language: en-US To: Michael Paquier , Justin Pryzby Cc: Andrew Dunstan , Bruce Momjian , Tom Lane , pgsql-hackers@lists.postgresql.org References: <20211212025017.GN17618@telsasoft.com> <20211215210916.GC4440@momjian.us> <711370.1639603043@sss.pgh.pa.us> <20211215212343.GE4440@momjian.us> <20211215221310.GU17618@telsasoft.com> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 16.12.21 02:39, Michael Paquier wrote: > On Wed, Dec 15, 2021 at 04:13:10PM -0600, Justin Pryzby wrote: >> On Wed, Dec 15, 2021 at 05:04:54PM -0500, Andrew Dunstan wrote: >>> The directory name needs to be predictable somehow, or maybe optionally >>> set as a parameter. Having just a timestamped directory name would make >>> life annoying for a poor buildfarm maintainer. Also, please don't change >>> anything before I have a chance to adjust the buildfarm code to what is >>> going to be done. >> >> Feel free to suggest the desirable behavior. >> It could write to pg_upgrade.log/* and refuse to run if the dir already exists. > > Andrew's point looks rather sensible to me. So, this stuff should > have a predictable name (pg_upgrade.log, pg_upgrade_log or upgrade_log > would be fine). But I would also add an option to be able to define a > custom log path. The latter would be useful for the regression tests > so as everything gets could get redirected to a path already filtered > out. Could we make it write just one log file? Is having multiple log files better?