Amigos,

Criei uma pequena PL para auxiliar essa "varredura":

http://fabriziomello.blogspot.com/2009/01/postgresql-procurar-determinado-oid-no.html


2009/1/10 Fabrízio de Royes Mello <[email protected]>

> Agora que o amigo Osvaldo publicou é bem isso mesmo... há alguns meses
> passei por esse mesmo problema e tive de vasculhar o catálogo pra tentar
> achar o maldito OID com problema e apagá-lo...
>
> Isso até dá pra fazer uma pequena PL pra varrer o catálogo em busca do OID
> e retornar onde ele encontrou ;)
>
> Abraço,
>
>
> 2009/1/10 Osvaldo Kussama <[email protected]>
>
>> Em 10/01/09, Sebastian SWC<[email protected]> escreveu:
>> > 2009/1/10 Osvaldo Kussama <[email protected]>:
>> >> 2009/1/10, Sebastian SWC <[email protected]>:
>> >>> Pessoal , ao executar o pg_dump no meu servidor ocorre o erro abaixo:
>> >>>
>> >>> # pg_dump -U postgres -d jetclass -v -Fc -f banco.backup -n public
>> >> Rode um reindexdb em seu banco.
>> >> Depois rode:
>> >> SELECT oid,* FROM pg_namespace;
>> >
>> > já rodei, só que não mudou nada.  com essa query (SELECT oid,* FROM
>> > pg_namespace;) eu tenho 260 "schemas" sendo que 256 são do tipo
>> > pg_temp....
>> >
>>
>>
>> Rodei aqui e obtive o seguinte:
>> kuss...@knotebook:~$ pg_dump -U postgres -d -v -Fc -f banco.backup -n
>> public bdteste
>> pg_dump: reading schemas
>> pg_dump: reading user-defined functions
>> pg_dump: reading user-defined types
>> pg_dump: reading procedural languages
>> pg_dump: reading user-defined aggregate functions
>> pg_dump: reading user-defined operators
>> pg_dump: reading user-defined operator classes
>> pg_dump: reading user-defined text search parsers
>> pg_dump: reading user-defined text search templates
>> pg_dump: reading user-defined text search dictionaries
>> pg_dump: reading user-defined text search configurations
>> pg_dump: reading user-defined operator families
>> pg_dump: reading user-defined conversions
>> pg_dump: reading user-defined tables
>> pg_dump: reading table inheritance information
>> pg_dump: reading rewrite rules
>> pg_dump: reading type casts
>> pg_dump: finding inheritance relationships
>> pg_dump: reading column info for interesting tables
>> ...
>>
>> Tente rodar:
>> SELECT * FROM  pg_type WHERE oid = 264202372;
>>
>> SELECT * FROM  pg_language WHERE oid = 264202372;
>>
>> e assim por diante (pg_aggregate, pg_operator, ...), para ver se
>> consegue determinar onde está ocorrendo o problema.
>>
>> Osvaldo
>> _______________________________________________
>> pgbr-geral mailing list
>> [email protected]
>> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
>>
>
>
>
> --
> Fabrízio de Royes Mello
> >> Blog sobre PostgreSQL: http://fabriziomello.wordpress.com
>



-- 
Fabrízio de Royes Mello
>> Blog sobre PostgreSQL: http://fabriziomello.blogspot.com
_______________________________________________
pgbr-geral mailing list
[email protected]
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral

Responder a