Thread: BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration)

The following bug has been logged on the website:

Bug reference:      18700
Logged by:          Jose Reyes
Email address:      jose.reyes@prswservices.com
PostgreSQL version: 16.3
Operating system:   Windows 11 24H2
Description:

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. The import did not work with a Custom dump, and when I
tried with a Plain dump I examined the SQL it produced an couldn't find any
statements to create either collations nor types.

I scoured the PgAdmin 4 and pg_dump documentation and found no mention of
these classes. Ended up working around it by inserting the SQL required for
the tasks.

Please look into this and let me know, as I'm somewhat surprised I haven't
found anything on the internet about this specific situation.

Thanks,

Jose

PG Bug reporting form <noreply@postgresql.org> 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