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 1nATnY-0002Lb-Gu for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Jan 2022 09:32:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nATn1-000785-0X for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Jan 2022 09:31:31 +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 1nATmz-00077w-OB for pgsql-hackers@lists.postgresql.org; Thu, 20 Jan 2022 09:31:30 +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 1nATmr-0006D6-TD for pgsql-hackers@lists.postgresql.org; Thu, 20 Jan 2022 09:31:28 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 4CDC53201FCD; Thu, 20 Jan 2022 04:31:19 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 20 Jan 2022 04:31:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Q8Tivx1bhooygx0i90LpHWqTTol2Kif3LgtMvJ1Oc b4=; b=NrvZw1kCfjMFjTnKQgyCKgAa+/kU4AsWhvTMCYVdOFSddp/5sLRmH5yE2 ixsRT4DBJQtHBv82m0PfBTW3/oCKdZDSucVwuXF7WrMTWxSWNJ3PcCrn/qjBDDf6 9oa0hhx6fftkyTOZC1wjizRAht9XhsxK27rSShTPg+rju8tVrJ/rH4hTV5OEw0ug EAdVdoOsKpZ/Eq2HNEfuQneso/roiubgT7KJKZPvTez8ToEJWb4a2lB9IHv5PgK3 oZc7qMeQ+qINNnFNhMMNucC8dROPIiH6kKO8dc6lEUG4joxyZJIu+8lRKqkV3XSo vDVgd6e6/fX/tX62echLDG8QpBPwQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudekgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 20 Jan 2022 04:31:16 -0500 (EST) Message-ID: <45e7680a-b617-1397-afa0-35a793aacefe@enterprisedb.com> Date: Thu, 20 Jan 2022 10:31:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: pg_upgrade should truncate/remove its logs before running Content-Language: en-US To: Michael Paquier , Justin Pryzby Cc: Tom Lane , Daniel Gustafsson , Andrew Dunstan , Bruce Momjian , pgsql-hackers@lists.postgresql.org References: <20211221033926.GX17618@telsasoft.com> <238201.1640184746@sss.pgh.pa.us> <20211222163611.GC17618@telsasoft.com> <20220108184857.GI14051@telsasoft.com> <20220111200307.GA14051@telsasoft.com> <20220112040813.GD14051@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 19.01.22 09:13, Michael Paquier wrote: > - Renaming of the option from --logdir to --outputdir, as this does > not include only logs. That matches also better with default value > assigned in previous patches, aka pg_upgrade_output.d. I'm afraid that is too easily confused with the target directory. Generally, a tool processes data from input to output or from source to target or something like that, whereas a log is more clearly something separate from this main processing stream. The desired "output" of pg_upgrade is the upgraded cluster, after all. A wildcard idea is to put the log output into the target cluster.