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 1q46MF-0007in-Jn for pgsql-general@arkaria.postgresql.org; Tue, 30 May 2023 20:54:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q46ME-0008No-Af for pgsql-general@arkaria.postgresql.org; Tue, 30 May 2023 20:54:18 +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 1q46ME-0008Nf-0F for pgsql-general@lists.postgresql.org; Tue, 30 May 2023 20:54:18 +0000 Received: from mail-yw1-x112a.google.com ([2607:f8b0:4864:20::112a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q46MA-0038rJ-DG for pgsql-general@lists.postgresql.org; Tue, 30 May 2023 20:54:17 +0000 Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-568ba7abc11so23182387b3.3 for ; Tue, 30 May 2023 13:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685480053; x=1688072053; h=content-transfer-encoding:subject:from:content-language:to :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=Gy18P/YKY1+zv3/HnMx7Ecnm2HJaGl8J4T5jQB+qtaw=; b=fX5aF6uQkW15/5a/gjHIoCUKz/D5HG1lxcLumSj8yvzCv5JQB1dlkFp8MX8OGO+xeT 5ekhGo1aMfbQEq3f3QEC6v9jPIP2bMFjFqI2MCm/xHzicju0L24XLgsst8WEoTsoZNd0 u2WArvS9DWFW2rP0puZ/OV9im434KzTRf3hwSf0/2BFjhNe4wOR9d3TaFR4pTYie04SU 3M1SzHXp+s3DBebdRMdhbpybYOjeMbKljaLthOnpt7bvqFJsE6oXbMYgR9wMM0ZtW505 DKD9bwUTFLBaA5uqJbxOFelZgyGvItb8/0XCmxHzXeCSkit/mvkqV7TDp5zuPuw7pflz HyYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685480053; x=1688072053; h=content-transfer-encoding:subject:from:content-language:to :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=Gy18P/YKY1+zv3/HnMx7Ecnm2HJaGl8J4T5jQB+qtaw=; b=PQtOmuv62QgbC1FCyKIlSGv0BBfBtrGATfQIBPmNtv9VzfN0I890e3RYl/SqVB8kpN i8aV4CQPHfBfclXOqba34ilffo0UFDlQziqobm32MWw8Ejk/8wsAmN1KYiOVC9zUsasA meZDVyKYwmoaDqZ/QCH7qDxK8GvkXiCh8D1swj6ceUrcYnHoRXlP5R8NckKaHqlRScp1 7IqH2N0bllwv9QpvhDw8N75T4Ag/zXpK3e/UDEAaF36B+vBO3hWf5A2CpYScyMQ9hkRI 1og8bsM6C0El6LMoSaJrIFEcMhsHJy1nHSawrlRbnEjPavku3ue5q6u6HXpFoImhTAt8 tUpA== X-Gm-Message-State: AC+VfDxr5qIrwM4dy2GKRmUJ12OsNB4exh3qtinZPn48jhZlOvtP96Wk uJTPh84VXF5jlEQyO0jvpXjMivmMDrY= X-Google-Smtp-Source: ACHHUZ6mM5HQmImY3Yi7VUAr/GOHbNdo4e+FiXudTn8Fww+a+/bRb48cjByWyjeRn2GMfmb8NJjjdw== X-Received: by 2002:a81:84c7:0:b0:567:7db6:3d48 with SMTP id u190-20020a8184c7000000b005677db63d48mr4124241ywf.12.1685480052756; Tue, 30 May 2023 13:54:12 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:3452:d680:5c16:927d? ([2600:1700:bd2c:b810:3452:d680:5c16:927d]) by smtp.googlemail.com with ESMTPSA id o185-20020a8173c2000000b00545a08184edsm4780560ywc.125.2023.05.30.13.54.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 May 2023 13:54:12 -0700 (PDT) Message-ID: <7e1a8736-d74c-8de1-679f-f47b250a13cc@gmail.com> Date: Tue, 30 May 2023 15:54:11 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 To: pgsql-general@lists.postgresql.org Content-Language: en-US From: Ron Subject: Pg 16: will pg_dump & pg_restore be faster? 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 https://www.postgresql.org/about/news/postgresql-16-beta-1-released-2643/ says "PostgreSQL 16 can also improve the performance of concurrent bulk loading of data using COPY up to 300%." Since pg_dump & pg_restore use COPY (or something very similar), will the speed increase translate to higher speeds for those utilities? -- Born in Arizona, moved to Babylonia.