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 1nUPOO-00039P-WF for pgsql-docs@arkaria.postgresql.org; Wed, 16 Mar 2022 08:52:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUP0y-0008Kz-Gy for pgsql-docs@arkaria.postgresql.org; Wed, 16 Mar 2022 08:28:16 +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 1nUP0y-0008Kq-9g for pgsql-docs@lists.postgresql.org; Wed, 16 Mar 2022 08:28:16 +0000 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nUP0p-0004t6-B3 for pgsql-docs@lists.postgresql.org; Wed, 16 Mar 2022 08:28:15 +0000 Received: by mail-ed1-x533.google.com with SMTP id g20so1755406edw.6 for ; Wed, 16 Mar 2022 01:28:07 -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:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=u2722SAZ3X4OpTFG/G0Tg+o5QWJPgTickQ3HT8S0xek=; b=oB40qL1ZQZwHeNKVh2nQqYJChJp7g87wZkmiNu65p4T9EIufhtBIpKt0kxjDkD2Ddc OTlBdbVthX0QNN5mg9jQfw2S9hLHt+bmmMo9StslV/YWD7d7qut0nJGO9Y8mEtw8amKq oKPrC1ZicJPMwutmkg0DZX5DZBpp/nninQb79nZrtA8mu54gTFPx50oEFPlx9ThgOK5C Aek9mwE7VDJZUBl/fwom+HvSJJnzAdmtBhLHWQj7XWbikD9pBiGk4XADu1gD6+Tqck13 MWyCUWxjHUvETvyPJVBTeKkqTZCTzHWdqjPtJKMrZXu4xbxwwfnzZp4MNnGy6hk9pTAh Ue9w== 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:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=u2722SAZ3X4OpTFG/G0Tg+o5QWJPgTickQ3HT8S0xek=; b=PI2PYSNl5savjSZI9Ioej9F8QgNYSfZnHoE996Gif8qJQ+7v5tE9TR5TLTiYpcN4Z6 wR/yn6gEpV8JYJG0U2HzYEF2iH6f/QFM8myyFhN2Rj91wVoDBez8s8MG9BHG7wRaNr7q KB0weDsf8l63Si2Y0/BLO1BI0hUNmWVXXyYm7clhJFb7waE6MKN4vnv0SMX/5Fro0ugC 3P5OxdOercKc5zJwBr3bg6ODNyiMB12FkQChuLHFbj/fXhyjiyh69enWpiyJZRSiAGDE +gk48D/6vqUG8sF6svatZZwDvkSzpwB+BHsaM8ZG+HfMt6SrOfVH+uWp0rVmbWUDXuHx xmzA== X-Gm-Message-State: AOAM5335YM2pJjom10+0Rh4cQsKLPQh+NUK4wiYzD8xuHw4g0Hufoek+ S4BQOeVyd3UQDVH3opr9gKSUIQ== X-Google-Smtp-Source: ABdhPJzeadDi4X+ZlnxYjIBoLBC+Pkj4s30FtPzuq9bVuAUcssccmyQ5D1Ksz/xQNU+aB3xjJVyVJg== X-Received: by 2002:a05:6402:50c9:b0:418:7fbc:14ee with SMTP id h9-20020a05640250c900b004187fbc14eemr13780187edb.53.1647419285699; Wed, 16 Mar 2022 01:28:05 -0700 (PDT) Received: from localhost.localdomain ([88.116.133.170]) by smtp.gmail.com with ESMTPSA id j20-20020a508a94000000b00416c19650e8sm608147edj.71.2022.03.16.01.28.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Mar 2022 01:28:05 -0700 (PDT) Message-ID: <45e991f00a7a5b81aadf984ccbe27f9c812d780d.camel@cybertec.at> Subject: Re: "Restore" vs. "Reload" From: Laurenz Albe To: axel.kluener@gmail.com, pgsql-docs@lists.postgresql.org Date: Wed, 16 Mar 2022 09:28:04 +0100 In-Reply-To: <164736074430.660.3645615289283943146@wrigleys.postgresql.org> References: <164736074430.660.3645615289283943146@wrigleys.postgresql.org> 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: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2022-03-15 at 16:12 +0000, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/14/backup-dump.html > > As far as I can see, the terms "Reload" and "Restore" are used > interchangeably. > To make the page as easy digestable for the reader as possible, it´s > advisable to stick to exactly one term. That makes sense, particularly since "reload" typically means something else in PostgreSQL. I think "restore" is better. Do you feel like preparing a patch? Yours, Laurenz Albe