Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TCXMy-00054M-7c for pgsql-sql@postgresql.org; Fri, 14 Sep 2012 14:59:48 +0000 Received: from mail-pz0-f46.google.com ([209.85.210.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TCXMw-0003su-M1 for pgsql-sql@postgresql.org; Fri, 14 Sep 2012 14:59:47 +0000 Received: by dady13 with SMTP id y13so2469276dad.19 for ; Fri, 14 Sep 2012 07:59:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qP+dJJDdXaMDtDQSJlaXryYnEV67k8wzSpZH1ssQE2s=; b=jz9J4QhseuxCVCIMDIJMQks0/rjxwbmm4AXK82jIVHsonw629gGu4CWsMOdZLSa98l 2a+oW7YVp10srNIWl4LFF3a35JyWwwIK7xu16SB93897+AZwQ1GIv4TTzXdfSlattJZo Bt55hpD0Ht424wFZhoRY4dLLU1Y7RdyxDYRBjkaD3qJZoeiH/h5PUFr2it8j9nek+1xP 9zbqpTi3Z2Bu2xMzQZ4r6ttJ3gPklQSQHYMhRkAG05g7HU0r6HN2ikkkz/m8YbGq77t2 SXsTmqgDQkCSuMDls556NqdtTFKqpT0QEoWLe5C/J/pCGNk0TATQqXv3TH8zp5JMVtUo usmA== Received: by 10.68.189.70 with SMTP id gg6mr5463087pbc.125.1347634785727; Fri, 14 Sep 2012 07:59:45 -0700 (PDT) Received: from [192.168.0.3] (c-24-17-164-54.hsd1.wa.comcast.net. [24.17.164.54]) by mx.google.com with ESMTPS id pj8sm1102378pbb.60.2012.09.14.07.59.43 (version=SSLv3 cipher=OTHER); Fri, 14 Sep 2012 07:59:45 -0700 (PDT) Message-ID: <50534600.6050801@gmail.com> Date: Fri, 14 Sep 2012 07:58:08 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: =?UTF-8?B?S2plbGwgw5h5Z2FyZA==?= CC: pgsql-sql@postgresql.org Subject: Re: pg_restore problem References: <5051E39B.3080803@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201209/42 X-Sequence-Number: 36844 On 09/14/2012 01:58 AM, Kjell Øygard wrote: > 1 - Ok, I was not aware of that.... > 2 - I used version 9.1.4 of pg_dump > 3 - The command was in a script, se below > > pdir=/usr/local/postgresql-9.1.4/ > bdir=/backup/`hostname -s`/dump/ > export PATH=${pdir}/bin:$PATH > > # make sure tmp files are not readable by others > umask 0077 > > for db in `psql -l -t -h localhost | awk '{print $1}' |grep -v > template|grep -v postgres` > do > pg_dump -h localhost -F c -Z -b $db > ${bdir}/${db}.tmp && mv > ${bdir}/${db}.tmp ${bdir}/${db}.dump I do not see anything obviously wrong. Two suggestions. 1) Use the 9.2 version of pg_dump. Newer versions know about changes in data handling and are also backward compatible(to 7.0). 2) As of 8.3(I believe) the -b switch is redundant for whole database dumps. When you do the above dump are there large objects in the 9.2 database in spite of the errors? > > > rgds Kjell Inge Ø > -- Adrian Klaver adrian.klaver@gmail.com