Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 5BD049FA5A7 for ; Wed, 12 Sep 2007 19:48:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 37109-04 for ; Wed, 12 Sep 2007 19:48:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 4750C9FA59B for ; Wed, 12 Sep 2007 19:48:23 -0300 (ADT) Received: from perhan.alvh.no-ip.org ([190.95.8.15]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l8CMmNii014011; Wed, 12 Sep 2007 15:48:24 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 96DFF47C68; Wed, 12 Sep 2007 18:48:21 -0400 (CLT) Date: Wed, 12 Sep 2007 18:48:21 -0400 From: Alvaro Herrera To: DIEGO ARMANDO LOPEZ PINILLA Cc: pgsql-admin@postgresql.org Subject: Re: Telecom(Colombia) - Error postgresql Message-ID: <20070912224821.GF6627@alvh.no-ip.org> References: <410F18AA90054F4F96A520CA757D556C02FF14D1@WBOGEX01.telecom.esp> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <410F18AA90054F4F96A520CA757D556C02FF14D1@WBOGEX01.telecom.esp> User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.91.1/4255/Wed Sep 12 00:18:47 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 12 Sep 2007 15:48:25 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/86 X-Sequence-Number: 26847 DIEGO ARMANDO LOPEZ PINILLA wrote: > De pronto me podrían colaborar con la solución de este inconveniente: > > postgres@lbogap02:~> pg_dump tollticketing > prueba.backup > > pg_dump: schema with OID 128157747 does not exist El problema es que hay un catalogo que hace referencia a ese schema, que no existe. La solucion pasa por saber cual es ese catalogo. No hay muchos catalogos que tengan un namespace; prueba lo siguiente: select attrelid::regclass, attname from pg_attribute join pg_class on (oid = pg_attribute.attrelid) where attname like '%namespace' and relkind = 'r'; Eso te va a dar un listado de catalogos y el nombre de la columna. A continuacion, para cada nombre del listado, haz select * from pg_type where typnamespace = '128157747'; (reemplaza nombre de catalogo y columna segun corresponda). Cuando encuentres uno que tiene ese valor, muestralo aca y vemos que se hace con el. -- Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J "Before you were born your parents weren't as boring as they are now. They got that way paying your bills, cleaning up your room and listening to you tell them how idealistic you are." -- Charles J. Sykes' advice to teenagers