Re: Cannot pg_dump_all anymore...

Поиск
Список
Период
Сортировка
От E-BLOKOS
Тема Re: Cannot pg_dump_all anymore...
Дата
Msg-id d19f56a4-c6ae-435f-9e6e-a1cad0f78271@e-blokos.com
обсуждение исходный текст
Ответ на Re: Cannot pg_dump_all anymore...  (Greg Sabino Mullane <htamfids@gmail.com>)
Ответы Re: Cannot pg_dump_all anymore...
Список pgsql-general


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

--
Enterprise Postgres Software Products & Tech Support

ok I fixed it with:

SELECT * FROM pg_depend WHERE objid IN (794964, 794968);
DELETE FROM pg_depend WHERE objid IN (794964, 794968);

systemctl restart postgresql

is it possible a crash happened with a VACUUM and a machine reboot in same time?

-- 
E-BLOKOS

В списке pgsql-general по дате отправления: