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 1mKijn-0004Yr-IJ for pgsql-general@arkaria.postgresql.org; Mon, 30 Aug 2021 14:58:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mKijm-0007FJ-Ih for pgsql-general@arkaria.postgresql.org; Mon, 30 Aug 2021 14:58:14 +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 1mKijm-0007FB-9m for pgsql-general@lists.postgresql.org; Mon, 30 Aug 2021 14:58:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mKijk-00073T-9K for pgsql-general@lists.postgresql.org; Mon, 30 Aug 2021 14:58:13 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 17UEw7FT1351365; Mon, 30 Aug 2021 10:58:08 -0400 From: Tom Lane To: depesz@depesz.com cc: Laurenz Albe , pgsql-general Subject: Re: Can we get rid of repeated queries from pg_dump? In-reply-to: <20210830144551.GA27054@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> <20210830074442.GB15241@depesz.com> <1349119.1630332682@sss.pgh.pa.us> <20210830144551.GA27054@depesz.com> Comments: In-reply-to hubert depesz lubaczewski message dated "Mon, 30 Aug 2021 16:45:51 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1351363.1630335487.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Aug 2021 10:58:07 -0400 Message-ID: <1351364.1630335487@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk hubert depesz lubaczewski writes: > On Mon, Aug 30, 2021 at 10:11:22AM -0400, Tom Lane wrote: >> I speculate that it is collecting and then not printing the info >> about functions that are in extensions --- can you check on >> how many there are of those? > classid =E2=94=82 count = > =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=BC=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 > pg_type =E2=94=82 31 > pg_proc =E2=94=82 1729 > pg_class =E2=94=82 61 > pg_foreign_data_wrapper =E2=94=82 1 > pg_cast =E2=94=82 30 > pg_language =E2=94=82 1 > pg_opclass =E2=94=82 73 > pg_operator =E2=94=82 111 > pg_opfamily =E2=94=82 73 > (9 rows) Ah-hah. Those 1729 extension-owned functions account nicely for the extra probes into pg_proc, and I bet they are causing the unexplained getFormattedTypeName calls too. So the *real* problem here seems to be that we're doing too much work on objects that are not going to be dumped because they are extension members. I'll take a look at that later if nobody beats me to it. regards, tom lane