X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0E5C653547 for ; Wed, 30 Mar 2005 22:44:16 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 58573-08 for ; Wed, 30 Mar 2005 21:44:07 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 0B36B53524 for ; Wed, 30 Mar 2005 22:44:07 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j2ULi4pU059941 for ; Wed, 30 Mar 2005 21:44:04 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j2ULg4i3059394 for pgsql-admin@postgresql.org; Wed, 30 Mar 2005 21:42:04 GMT (envelope-from news) From: Dario X-Newsgroups: pgsql.admin Subject: postgres 7.2.1 pg_restore large objects Date: Wed, 30 Mar 2005 18:41:43 -0300 Organization: Hub.Org Networking Services Lines: 100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: usenet@news.hub.org User-Agent: Opera M2/7.54 (Win32, build 3865) To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/496 X-Sequence-Number: 16994 Problem: Not being able to restore a database with lo. I have already re= ad = forums and doc. Probably I'm loosing something, but I just can figure. Reading forums I though I finally got a "right" way to do it. I'm running this as OS user "postgres" which is a super user pg_dump -Ft -o -b base > base.tar 2>log_err2 # If I untar the file, i se= e = table data, and blob data, toc and restore.sql. createdb base2 //from OS shell /usr/local/pgsql/bin/pg_restore -Ft -s -v -d base2 base.tar 2>elogerr = = #creates schema psql -f src/contrib/lo.sql base2 #creates lo type and functions... my= = base.tar includes lo type definition. O also tried to delete the type = previously, and did not make any difference. If I do not do this, = pg_restore claims that I lo and oid must be explicity casted. One more = thing, I can't make lo_manage to work (trigger type doesn't exist). I do= n = use it anyway, since I manage lo updates and delete from app. I delete = blobs from app. /usr/local/pgsql/bin/pg_restore -Ft -a -v -d base2 base.tar 2>flogerr the pg_restore fails with the following error. ---------------------------------- pg_restore log (flogerr file) pg_restore: [archiver (db)] error while updating column "tca_texto" of = table "tca": server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. pg_restore: *** aborted because of error ---------------------------------- postgres log file DEBUG: server process (pid 25276) was terminated by signal 11 DEBUG: terminating any other active server processes NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. DEBUG: all server processes terminated; reinitializing shared memory an= d = semaphores ---------------------------------- No table is updated. I tried to create a table with oid column instead of lo, restore (worked= = in this way), I renamed table, I created a table with lo datatype, but = when I tried to insert into ... , same error occurs. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. I have two different versions of postgres, one compiled by someone here,= = and another version, installed via rpm. unlikely, upgrading to a different version, is not an option, I probably= = update to 7.2.(last version), but only if this specific problem is solve= d. = I have read the release section of the doc and did not apeared explicity= ... greetings. TIA to all "Hoy es un buen dia para morir" (today is a good day to die, Klingon en = = espa=F1ol)!