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 1tvCRX-001uDu-0i for pgsql-general@arkaria.postgresql.org; Thu, 20 Mar 2025 09:44:03 +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 1tvCRV-000opW-8c for pgsql-general@arkaria.postgresql.org; Thu, 20 Mar 2025 09:44:01 +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 1tuiyv-00AOM4-Gn for pgsql-general@lists.postgresql.org; Wed, 19 Mar 2025 02:16:33 +0000 Received: from [2001:bc8:1203:362::1] (helo=ns117.e-blokos.com) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tuiyr-003c8o-0j for pgsql-general@lists.postgresql.org; Wed, 19 Mar 2025 02:16:32 +0000 Received: from [127.0.0.1] (ip6-localhost [127.0.0.1]) by mail.e-blokos.com (8.18.1/8.18.1) with ESMTP id 52J2GOm4013947 for ; Wed, 19 Mar 2025 02:16:25 GMT Content-Type: multipart/alternative; boundary="------------0IOSPstoSw6LgJYbikwWtI6q" Message-ID: <35dafa40-372e-4fd8-bc52-d83833cafc81@e-blokos.com> Date: Tue, 18 Mar 2025 19:16:23 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Cannot pg_dump_all anymore... Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <92435272-360f-48fa-8ca0-a4ea89359c80@e-blokos.com> From: E-BLOKOS In-Reply-To: X-Host-Lookup-Failed: Reverse DNS lookup failed for 2001:bc8:1203:362::1 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------0IOSPstoSw6LgJYbikwWtI6q Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 --------------0IOSPstoSw6LgJYbikwWtI6q Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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

--------------0IOSPstoSw6LgJYbikwWtI6q--