public inbox for [email protected]
help / color / mirror / Atom feedFrom: E-BLOKOS <[email protected]>
To: [email protected]
Subject: Re: Cannot pg_dump_all anymore...
Date: Tue, 18 Mar 2025 19:16:23 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKAnmmJ=OupUu_4N3nQWYAfwCN6aT4s1PKQypHmpPLnX5Bz6qg@mail.gmail.com>
References: <[email protected]>
<CAKAnmmJ=OupUu_4N3nQWYAfwCN6aT4s1PKQypHmpPLnX5Bz6qg@mail.gmail.com>
On 3/18/2025 5:49 AM, Greg Sabino Mullane wrote:
> 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
>
select oid, typname, typtype, typnamespace::regnamespace from pg_type
where oid <= 794978 order by 1 desc limit 3;
oid | typname | typtype | typnamespace
--------+------------+---------+--------------
794970 | log_17167 | c | repack
794969 | _log_17167 | b | repack
794966 | pk_17167 | c | repack
(3 rows)
Arggh it's repack 🙁
I have no clue how to repair repack....
--
E-BLOKOS
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Cannot pg_dump_all anymore...
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox