Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rIuJv-00ArqV-Qu for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Dec 2023 17:37:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rIuJu-000Wza-HZ for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Dec 2023 17:37:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rIuJu-000WzO-2V for pgsql-hackers@lists.postgresql.org; Thu, 28 Dec 2023 17:37:22 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rIuJr-00CdMb-F3 for pgsql-hackers@lists.postgresql.org; Thu, 28 Dec 2023 17:37:20 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=vvKfvOy1EAL5ghLdAaYcRmicVVsquF0OH9ssGfPH9Qw=; b=0p8A5VHscrtzZqxPFtBvRBU/Xo cTLGsbHC1YJJgEeK+BDS5xyYhgxRHxhg7BI4vCT5xzClXjCicEo4ILq7uzlON735R2zPFWBXEdlqa 7BA94rtoH3C6ZLG/h6gg9kFUwb75QGYU7y8j2AjVq7gv2VfCpYOMJd4n1w5wWEW24XA3Goa1BVHC1 uXekz8+PwcifAEdGJY0vCsO9cp9XhL21BvBDSralxhBEUeKc0u7t52k4bxAY3fZ8VTnkQS7NIDPJk sHm2EkJOg4x2KMQ8gFIMFLKh+dpZez01NKAnz9hNAuowU6aI0GIjpnIiRzjH8IGmHU4ia+mim2MtB gr9YvSRg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1rIuJo-000872-32; Thu, 28 Dec 2023 12:37:16 -0500 Date: Thu, 28 Dec 2023 12:37:16 -0500 From: Bruce Momjian To: Corey Huinker Cc: Tom Lane , Tomas Vondra , Ashutosh Bapat , pgsql-hackers@lists.postgresql.org Subject: Re: Statistics Import and Export Message-ID: References: <76596388-6fe6-0baf-351d-734458a46d76@enterprisedb.com> <4268d862-7784-f76f-d7f1-359b0b4db67c@enterprisedb.com> <2090613.1703618344@sss.pgh.pa.us> <4e49c72e-f8a5-de1a-4ef4-36529bee1d65@enterprisedb.com> <2788275.1703733025@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Dec 28, 2023 at 12:28:06PM -0500, Corey Huinker wrote: > What I am proposing is *import* functions.  I didn't say anything about > how pg_dump obtains the data it prints; however, I would advocate that > we keep that part as simple as possible.  You cannot expect export > functionality to know the requirements of future server versions, > so I don't think it's useful to put much intelligence there. > > True, but presumably you'd be using the pg_dump/pg_upgrade of that future > version to do the exporting, so the export format would always be tailored to > the importer's needs. I think the question is whether we will have the export functionality in the old cluster, or if it will be queries run by pg_dump and therefore also run by pg_upgrade calling pg_dump. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.