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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jose(dot)reyes(at)prswservices(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration)
Date: 2024-11-12 15:32:17
Message-ID: 1196269.1731425537@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2024-11-12 15:48:31 Re: HashAgg degenerate case
Previous Message Daniel Gustafsson 2024-11-12 14:56:07 Re: BUG #18675: Postgres is not realasing memory causing OOM