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 1tAssT-000dhc-9d for pgsql-bugs@arkaria.postgresql.org; Tue, 12 Nov 2024 15:32:24 +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 1tAssP-007X33-9v for pgsql-bugs@arkaria.postgresql.org; Tue, 12 Nov 2024 15:32:21 +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 1tAssP-007X2v-1G for pgsql-bugs@lists.postgresql.org; Tue, 12 Nov 2024 15:32:21 +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.94.2) (envelope-from ) id 1tAssM-001VRU-J7 for pgsql-bugs@lists.postgresql.org; Tue, 12 Nov 2024 15:32:20 +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 4ACFWHTe1196270; Tue, 12 Nov 2024 10:32:17 -0500 From: Tom Lane To: jose.reyes@prswservices.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration) In-reply-to: <18700-838f37945e913cbd@postgresql.org> References: <18700-838f37945e913cbd@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 11 Nov 2024 21:35:51 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1196268.1731425537.1@sss.pgh.pa.us> Date: Tue, 12 Nov 2024 10:32:17 -0500 Message-ID: <1196269.1731425537@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > While importing a whole database created with pg_dump (Windows Pg 16.3 and > PgAdmin 4 environment) to a Docker postgres:16.4-alpine3.20 container with > no data, the pg_restore command did not create any tables that used custom > collations or types. pg_dump surely has code for those things. You would need to provide far more detail (preferably, a reproducible example case) for anyone to figure out why things went wrong for you. https://wiki.postgresql.org/wiki/Guide_to_reporting_problems regards, tom lane