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 1urHMb-003Ukx-Tc for pgsql-general@arkaria.postgresql.org; Wed, 27 Aug 2025 14:43:03 +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 1urHMa-00FtYG-AG for pgsql-general@arkaria.postgresql.org; Wed, 27 Aug 2025 14:43:00 +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 1urHMZ-00FtY8-W7 for pgsql-general@lists.postgresql.org; Wed, 27 Aug 2025 14:43:00 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1urHMY-0021wN-0p for pgsql-general@lists.postgresql.org; Wed, 27 Aug 2025 14:42:59 +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 57REgvOk1392028; Wed, 27 Aug 2025 10:42:57 -0400 From: Tom Lane To: Ron Johnson cc: "pgsql-generallists.postgresql.org" Subject: Re: In-order pg_dump (or in-order COPY TO) In-reply-to: References: <3541781s-75o7-26pp-46pp-qs54o4406192@tzk.arg> <1389082.1756304193@sss.pgh.pa.us> Comments: In-reply-to Ron Johnson message dated "Wed, 27 Aug 2025 10:31:24 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1392026.1756305777.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 27 Aug 2025 10:42:57 -0400 Message-ID: <1392027.1756305777@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ron Johnson writes: > On Wed, Aug 27, 2025 at 10:16 AM Tom Lane wrote: >> Don't use --format=custom (and not -v either). That causes pg_dump to >> include the OIDs and pg_dump object IDs of all the tables and other >> objects, > That's interesting. Why? (Since isn't it supposed to be Bad to rely on > OIDs?) -v in a text-format dump includes that data for debugging purposes: -- -- TOC entry 1401 (class 1255 OID 16499) -- Name: fipshash(text); Type: FUNCTION; Schema: public; Owner: postgres -- (The "TOC entry" comment line wouldn't be there without -v.) Then custom format has to store the same info so that pg_restore can produce this identical text output on demand. Yeah, this is all pretty historical, but nobody wants to change it at this point. regards, tom lane