Potentially serious migration issue from 7.1.3 to 7.2 (or 7.3)

OK, I think I know. There are certain pg_dump format combinations that
can't be used together. I don't see your combination in the pg_dump.c
failure test routines, but you may have found a new one.

You are asking for oid's, custom output format, and blobs. Is it
possible that combination is broken in 7.1? Can you try a small test
with fewer options.

---------------------------------------------------------------------------

Joshua D. Drake wrote:

Hello,

We are experiencing some very strange behavior with a restore that we
are trying to do. The command we are using to do the backup is:

/bin/su - larry -c \"/usr/local/pgsql/bin/pg_dump $dbname
--superuser=larry -o --format=c -b -f /backups/$dbname.`date +%a`.tar.gz

The backups run, we appear unable to restore them. The command we are
using to try and restore the information is:

/usr/local/pgsql/bin/pg_restore -d dominion dominion.Fri.tar

When we run pg_restore we get the following -- thoughts???:

DEBUG: connection: host=[local] user=postgres database=dominion
DEBUG: InitPostgres
DEBUG: StartTransactionCommand
DEBUG: query: select getdatabaseencoding()
DEBUG: ProcessQuery
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: SELECT version()
DEBUG: ProcessQuery
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: select usesuper from pg_user where usename = 'postgres'
DEBUG: ProcessQuery
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: --
-- Selected TOC Entries:
--
--
-- TOC Entry ID 2 (OID 0)
--
-- Name: Max OID Type: <Init> Owner:
-- Data Pos: 0 (Length 0)
--

CREATE TEMPORARY TABLE pgdump_oid (dummy int4);
DEBUG: ProcessUtility: --
-- Selected TOC Entries:
--
--
-- TOC Entry ID 2 (OID 0)
--
-- Name: Max OID Type: <Init> Owner:
-- Data Pos: 0 (Length 0)
--

CREATE TEMPORARY TABLE pgdump_oid (dummy int4);
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query:
COPY pgdump_oid WITH OIDS FROM stdin;
DEBUG: ProcessUtility:
COPY pgdump_oid WITH OIDS FROM stdin;
pq_recvbuf: unexpected EOF on client connection
DEBUG: CommitTransactionCommand
pq_flush: send() failed: Broken pipe
pq_recvbuf: unexpected EOF on client connection
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)

--
<COMPANY>CommandPrompt - http://www.commandprompt.com </COMPANY>
<CONTACT> <PHONE>+1.503.222-2783</PHONE> </CONTACT>

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Hello,

O.k. that makes sense. I will take take out the OID and see what
happens. The most important is the blobs
as this is a database for a paperless office... I will report back my
findings.

Sincerely,

Joshua Drake

Bruce Momjian wrote: