| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | E-BLOKOS <infos(at)e-blokos(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Cannot pg_dump_all anymore... |
| Date: | 2025-03-18 12:49:22 |
| Message-ID: | CAKAnmmJ=OupUu_4N3nQWYAfwCN6aT4s1PKQypHmpPLnX5Bz6qg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
First figure out which database is having that issue, by using pg_dump
--schema-only on each database in turn. Then run this SQL on the database
giving the error to see if the type exists, or what is nearby:
select oid, typname, typtype, typnamespace::regnamespace from pg_type where
oid <= 794978 order by 1 desc limit 3;
Also let us know the version of pg_dump and the version of Postgres being
dumped.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evgeniy Ratkov | 2025-03-18 13:02:55 | Re: How to recover correctly master and replica using backup made by pg_basebackup? |
| Previous Message | Ron Johnson | 2025-03-18 10:59:22 | Re: Cannot pg_dump_all anymore... |