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 1tuWOS-009SOr-Lm for pgsql-general@arkaria.postgresql.org; Tue, 18 Mar 2025 12:50:04 +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 1tuWOR-00Dx3E-Cn for pgsql-general@arkaria.postgresql.org; Tue, 18 Mar 2025 12:50:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tuWOR-00Dx30-1s for pgsql-general@lists.postgresql.org; Tue, 18 Mar 2025 12:50:03 +0000 Received: from mail-il1-x12d.google.com ([2607:f8b0:4864:20::12d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tuWON-003Z3x-1X for pgsql-general@postgresql.org; Tue, 18 Mar 2025 12:50:02 +0000 Received: by mail-il1-x12d.google.com with SMTP id e9e14a558f8ab-3cda56e1dffso29483855ab.1 for ; Tue, 18 Mar 2025 05:50:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742302199; x=1742906999; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qNvS1S+LfN2szINY9k9CGR/0WFVreM/W4M7d/fqUrUs=; b=Vy7mqKF9OfT20XO6KcO0jg2Z17vtlTBJ41MhJoSSc3y/omEY61d3AwXtpkqXcOwn2q xprkonRXRaohW0EdeDR5bNEkwnwipxXeMZFedrEulFhonAkMlq40oK+4m1oWQ3DMMe4v UQXkI/75Q3FMw4JUHEZBsceSRR7f/MAZ1NuqbDlgIIQpg7djVa5RhNUKkBDbMhou1wsz jed2/D7u4DL70lvpiIiMS+KysMo9Pdlbbm//5uJ75qsH0X20uR7pYQOHO7YwxnhTTUEn MOKUjDiIQJvBvKdqTpNA3zup9LO2OXPPOQuJ/0wh1EGCkFXerR45FrrIVQgYprPkGBtg b54A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742302199; x=1742906999; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qNvS1S+LfN2szINY9k9CGR/0WFVreM/W4M7d/fqUrUs=; b=CvKYYgMIBlx2faO7gRpkYMd3kXxH8jg+YnFiNFeOkuv+va5ZVb3km0FAlochiXBWXf Zb/7IpYuqXZ/CRwsZTv3FfH5e6e5ub1hXDC18G+uokxsu8j5S9oXktfxiD8XIBwuVwgE ErB0fiqe2NlQ/X9nZ6yr9csmkfd4cwfc9P3mIgDWpHllxDz4/MZhSelDsXFxoDZmo8VS wE/TbeazFvj4DZVuTSKf07BmbAJlH6bJ0I+wnnC26rAw1SH9T5llfuXITKn52/kuFbQe bTOZh7CGfL+F79Mm66Kfbf0qHUA8n6f/jXKgXVVuybNDuvhH4b3u1xv3c3S/aIZvOfIc 6hPQ== X-Gm-Message-State: AOJu0YwGGVX6RKSSLHgyKxaQ/bg7nmaTNUaRYoXful4aGV6N1AeMFKDO 98ATa0kQIHhiVrMYP14ebU6opUz5fawGnGh+srWZ6FUt7Z75OIaf16iv+4m5jRz6rNkwornOoTX W1gI7w/NFct50uMGKwzo5HeQtbX2EyaNo X-Gm-Gg: ASbGncvt/iEav8gc8qagm7cfffsKdt+hwWBzqedAdNOiAJF+UrUFbHmeObrtnALZEec FXpTS2kC5Qf5MtHKCDVsy0tqBONFSQLSBwGkQVSyJqTOfFC1+H/gslHZit9nBeKzVJ0F7WLiamX Dqq0Itid57C+dwXak6uXn9d40MC8am3rwQxlA9DfniAuhbikIM6PaoT0H6l5/mhDEu8LDybcQ= X-Google-Smtp-Source: AGHT+IHklfxgzADo9iq4h2w5BLmYAi1ERX9NWXimfsnZ7akcLmj34SWgnHTThXshQD0IxGLHsvUy/u9iJHf6tuK1f2w= X-Received: by 2002:a05:6e02:1609:b0:3d4:3d63:e070 with SMTP id e9e14a558f8ab-3d483a7587fmr170088755ab.16.1742302199058; Tue, 18 Mar 2025 05:49:59 -0700 (PDT) MIME-Version: 1.0 References: <92435272-360f-48fa-8ca0-a4ea89359c80@e-blokos.com> In-Reply-To: <92435272-360f-48fa-8ca0-a4ea89359c80@e-blokos.com> From: Greg Sabino Mullane Date: Tue, 18 Mar 2025 08:49:22 -0400 X-Gm-Features: AQ5f1JrcLKaXpE4dO1RLCIbYQfGMZ4Ld64YH4qJD2oReWLoGz4Ha6-heruKxggk Message-ID: Subject: Re: Cannot pg_dump_all anymore... To: E-BLOKOS Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000aa9a6706309d5738" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aa9a6706309d5738 Content-Type: text/plain; charset="UTF-8" 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 --000000000000aa9a6706309d5738 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
First figure out which database is having= =C2=A0that 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 exist= s, or what is nearby:

select oid, typname, typtype, typn= amespace::regnamespace from pg_type where oid <=3D 794978 order by 1 des= c limit 3;

Also let us know the version of pg_dump= and the version of Postgres being dumped.


Cheers,
Greg

--
Enterprise Postgres Software Products & Tech S= upport

--000000000000aa9a6706309d5738--