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 1mJrzf-0001tP-RG for pgsql-general@arkaria.postgresql.org; Sat, 28 Aug 2021 06:39:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mJrz7-00020e-TS for pgsql-general@arkaria.postgresql.org; Sat, 28 Aug 2021 06:38:33 +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 1mJrz7-00020W-GZ for pgsql-general@lists.postgresql.org; Sat, 28 Aug 2021 06:38:33 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJrz0-00012W-W1 for pgsql-general@lists.postgresql.org; Sat, 28 Aug 2021 06:38:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ks08Imy7U4ij9vStej9E0Y6oazHj17tYqLP/C0Bu4G8=; b=KObjejkSlDHOqzLij08kjcNsIK Lfj/qksP8dN6TXZHfc59tWPPTug3HgXSjOYFDmOOuQ9NStw8OTcPoUduXN2bhmvmz8PK9Afssddcf DxQuEc060D782SUNJUiI0IZhzuRZE+olsGMvBkYdMjU1liKr831/5CmQgY9uZHWc/9gg=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1mJryy-0003F8-5t; Sat, 28 Aug 2021 08:38:24 +0200 Date: Sat, 28 Aug 2021 08:38:24 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Tom Lane Cc: Laurenz Albe , pgsql-general Subject: Re: Can we get rid of repeated queries from pg_dump? Message-ID: <20210828063824.GA11579@depesz.com> Reply-To: depesz@depesz.com References: <20210826084430.GA26282@depesz.com> <648517.1629986527@sss.pgh.pa.us> <20210826140827.GA15868@depesz.com> <649446.1629987629@sss.pgh.pa.us> <20210826160644.GA3120@depesz.com> <896732.1630099403@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <896732.1630099403@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Aug 27, 2021 at 05:23:23PM -0400, Tom Lane wrote: > I experimented with the attached, very quick-n-dirty patch to collect > format_type results during the initial scan of pg_type, instead. On the > regression database in HEAD, it reduces the number of queries pg_dump > issues from 3260 to 2905; but I'm having a hard time detecting any net > performance change. > (This is not meant for commit as-is; notably, I didn't bother to fix > getTypes' code paths for pre-9.6 servers. It should be fine for > performance testing though.) Hi, thanks a lot for this. Will test and report back, most likely on Monday, though. Best regards, depesz