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.kla...@gmail.com
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
