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 1nc317-000804-5z for pgsql-docs@arkaria.postgresql.org; Wed, 06 Apr 2022 10:36:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nc315-0001u6-Ej for pgsql-docs@arkaria.postgresql.org; Wed, 06 Apr 2022 10:35:59 +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 1nc315-0001tx-40 for pgsql-docs@lists.postgresql.org; Wed, 06 Apr 2022 10:35:59 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nc313-0004bA-54 for pgsql-docs@lists.postgresql.org; Wed, 06 Apr 2022 10:35:58 +0000 Received: by mail-ed1-x52d.google.com with SMTP id x20so2037377edi.12 for ; Wed, 06 Apr 2022 03:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=9I2BcKX1Q1xCGZ7egbPpY0hxpls0YT6UhfcUAlEdqWQ=; b=1lWS/nBpLqEO09aF1zY+WHMzJ5NnEhVTvGhH80ylTtU63SVBzkwyG5oTeVy+oquHOE v7hkMjIO1Icky3qC25jMmyt6Iu674TM+h53OV9dnlmp6p2H7hHg1/Cq6UujPSNEwoGhh a6+854SBc6AjDw8V9Fp9q9S4fuxU51uWWDksvP6CyKTANCmg26rxAo1e2ub2OmevGGuR 6RpuHJucxS8lu36roBBNJ+k1ZhwnNwlNKuYTlJMofTE1KmWvC6ZECwqpeaLpeb0NwCki 2hYB3wBfFTEhZrk9MVRkBjlNdaEj+SgSa2no15mUi/x4tmzIczFATou95CUcye3jG4P7 Wcsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=9I2BcKX1Q1xCGZ7egbPpY0hxpls0YT6UhfcUAlEdqWQ=; b=HrEbllNr5JiLce7okUIQGt40BAsMx/Ujjp4hWr5PUtPmp6brJSl+ibNaxPtLyLspbp LraWJwUpr1qncBS0laFnd2Ydz9Uw2FrPIYOu06xFK599i4YhuSfI2RlIA4cM+V36mCdN vtLkwLDSefpWHg27lxBPyUXhM229agdlzb3RiwoP2QTFCrND6lZMvILzskaZkvf+gH1z h9JxJRkt0+y+6aQleql8uK3a7Z8ro2AZKiyqGb0Ps23P5lrZspEvNNL7jlQSWx7C5GaQ WJ+/WX/fUrWK7Sv29ZznbEU11uWEArPDyR6SBHnzFg1hbHQIiQB56n7hJOiVgIx1YAK7 bOvQ== X-Gm-Message-State: AOAM5333gnlFYRyGYZUZHZfst3obcfyGG6otBuZuzGY/szRAfqCQfxUM FgFsnermy7XK8OznnkddfgzUy6UfRCFKZg== X-Google-Smtp-Source: ABdhPJwfQB+2iYHmn7Sj6AGzm2fHJOILdU0Ebp0MQAD88Ye34TGzbFdYTRzGbwz6SsMwz4hfZVF7oQ== X-Received: by 2002:aa7:c913:0:b0:41c:bde7:6548 with SMTP id b19-20020aa7c913000000b0041cbde76548mr8033070edt.404.1649241356231; Wed, 06 Apr 2022 03:35:56 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:d0af:8bef:79d2:7d17:96e2]) by smtp.gmail.com with ESMTPSA id gb3-20020a170907960300b006dfafbb4ba4sm6471945ejc.83.2022.04.06.03.35.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Apr 2022 03:35:55 -0700 (PDT) Message-ID: Subject: Re: Improve documentation for pg_upgrade, standbys and rsync From: Laurenz Albe To: Robert Haas , Stephen Frost Cc: pgsql-docs@lists.postgresql.org Date: Wed, 06 Apr 2022 12:35:55 +0200 In-Reply-To: References: <22f129004bb66cd91e1dfd3345a9787f5039f3ae.camel@cybertec.at> <20210519143135.GI20766@tamriel.snowman.net> <20210716131744.GA20766@tamriel.snowman.net> <20210726191126.GW20766@tamriel.snowman.net> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-3.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2022-04-05 at 12:38 -0400, Robert Haas wrote: > Also, let me express my general terror at the idea of anyone actually > using this procedure. I did, and I couldn't get it to work with absolute paths, and using relative paths seemed to me to be more intuitive anyway, hence the patch. Originally that was the only change I wanted to make to the documentation, but you know how it is: as soon as you touch something like this, someone will (rightly so) prod you and say "while you change this, that other thing there should also be improved", and the patch gets more and more invasive. I agree with the scariness of this, but I prefer to have it in the documentation anyway; at least as long as we have nothing better (which is always the enemy of the good). Yours, Laurenz Albe