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 1ptFmd-0003Sd-Jp for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 30 Apr 2023 22:44:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ptFmc-0007DC-8T for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 30 Apr 2023 22:44:42 +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 1ptFmb-0007D3-Uj for pgsql-pkg-debian@lists.postgresql.org; Sun, 30 Apr 2023 22:44:42 +0000 Received: from mail-il1-x12b.google.com ([2607:f8b0:4864:20::12b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ptFmY-0063FA-9b for pgsql-pkg-debian@postgresql.org; Sun, 30 Apr 2023 22:44:40 +0000 Received: by mail-il1-x12b.google.com with SMTP id e9e14a558f8ab-32f397b44dcso35835165ab.1 for ; Sun, 30 Apr 2023 15:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20221208.gappssmtp.com; s=20221208; t=1682894675; x=1685486675; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=fuu9jYHWUGgVNn8h+YFSQHAtJjd4bMD6UhJbDeHywzI=; b=o6KYWk2+76dK8nPx2ZR/cwcvvBtMLiJg5pT/qWfr8laeGDScWQpOPfcTiTeUFRy7kg T+XUQW7pn9ygiaNVFV3NyuhkLp2CDt7HROOWCZ7FLsp27AwDYzPUNf0am6w+fSjm6/8I +LjQqWLltKLPZJfuxl2DFCcxovoQkzpZo0sRgLNfZ3MQMmQqgpbRvmf36vjwGuFPsK5A zThw8Itfr7BgB3Qkq4O8zPyTLmmpJda2HP3OBIGwvYkzWjijRbPeO07wnnI3YaJJBZq/ S5WFwoByaijVk9S7vxFADq+mUxZj3tmmPTsGRaga2R+PFhvRYLVc/rUVIzPgoHVB9AJR 41uA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682894675; x=1685486675; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=fuu9jYHWUGgVNn8h+YFSQHAtJjd4bMD6UhJbDeHywzI=; b=etrDei1K+qKK5L03Rv7xwvlS9II53CSgG/IzY1HOMhuM66ZONL64HlFlSpE3mHNVkt 43mFHafvQeDFb28CHlreNye0odUnMo4gByi59kFIpgeMfexRyswqJkY5wP4wIfdwDS8g NK3yGEQdD1UtVUV4CgLCu4OOd9b3YnSq3799FSYLSo9fYeTs1x5GaL50+vXZyQ1lWwPZ ddOWirjAR85fXq+hJCtQ4KkxSxpWrPyaDz9/AgKU5z5McJI7U4NYEAU3OSERGw31WH7G +YdXnOAE44UF/Attr73/Iu3ypX9erWJ1tkT91mkr5F+Ockv1qWGAaswKipAcI9Iwv0Fv udzA== X-Gm-Message-State: AC+VfDxweujabKZlmkF0sT1Ogp5nSE3eFHYx97khTRcRT7fwUsCdFoK1 J3sOxkyw3CpRVk5BHBI11Q/6ug== X-Google-Smtp-Source: ACHHUZ4A+2pnjRipb3AvLPpeEsjfUQvTzZp76STRYFETX6b3ME/YMlb99tlZ7/iqOWG7VKyErzSPDw== X-Received: by 2002:a6b:cd89:0:b0:760:a739:52ea with SMTP id d131-20020a6bcd89000000b00760a73952eamr8132740iog.0.1682894675216; Sun, 30 Apr 2023 15:44:35 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id g70-20020a025b49000000b004142c6ec8bcsm1806154jab.18.2023.04.30.15.44.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 30 Apr 2023 15:44:34 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id B4BC7800BAC; Sun, 30 Apr 2023 17:44:33 -0500 (CDT) Date: Sun, 30 Apr 2023 17:44:33 -0500 From: Justin Pryzby To: Christoph Berg , pgsql-pkg-debian@postgresql.org Subject: Re: postgresql-common: use latest version of pg_dump/restore Message-ID: 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 On Sun, Apr 30, 2023 at 09:57:19PM +0200, Christoph Berg wrote: > Re: Justin Pryzby > > I added dump/restore to this list locally while updating a backup script > > Hmm, I thought that would void the ability to restore to the same old > version? > > source server version <= pg_restore <= pg_dump <= target server Maybe I'm misundertanding your diagram - did you mean this ? > source server version <= pg_dump <= pg_restore <= target server I think you're considering the issue where pg_dump support is dropped for very old versions - that'd be something that's like ~10 years old. For example if someone has a pg9.1 server, and then installs pg15 clients, which dropped support for v9.1. Wouldn't that be handled here for pg_dump, the same as for psql ? if ($version and $version < 9.2) { # psql 15 only supports PG 9.2+ -- Justin