public inbox for [email protected]  

help / color / mirror / Atom feed

Cannot pg_dump_all anymore...
2+ messages / 2 participants
[nested] [flat]

* Cannot pg_dump_all anymore...
@ 2025-03-17 20:52  E-BLOKOS <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: E-BLOKOS @ 2025-03-17 20:52 UTC (permalink / raw)
  To: pgsql-general

I got this error:

pg_dump: error: query returned 0 rows instead of one: EXECUTE 
dumpBaseType('794978')

any clue to solve it?

thanks

David







^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Cannot pg_dump_all anymore...
@ 2025-03-18 12:49  Greg Sabino Mullane <[email protected]>
  parent: E-BLOKOS <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Greg Sabino Mullane @ 2025-03-18 12:49 UTC (permalink / raw)
  To: E-BLOKOS <[email protected]>; +Cc: 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


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2025-03-18 12:49 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-03-17 20:52 Cannot pg_dump_all anymore... E-BLOKOS <[email protected]>
2025-03-18 12:49 ` Greg Sabino Mullane <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox