Skip site navigation (1) Skip section navigation (2)

pg_restore hangs on 'some' HP-UX machines

From: "Gopal Srinivasa" <srinivgo(at)india(dot)hp(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: pg_restore hangs on 'some' HP-UX machines
Date: 2005-07-14 16:35:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin

I am using PostgreSQL 7.4.2 on HP-UX systems. I am trying to pg_restore a
dump created using pg_dump with the following command-line:
 pg_dump -Fc -fcerdump -Uemt -p10864 cer

The dump only has one table "emt_str", with integers and strings as its
attributes. Essentially, the table stores some strings used by our
application. It has around 250+ records.

When I run pg_restore (this is on a different machine), pg_restore creates
the schema, but hangs while inserting data. The command-line I am using is:
 pg_restore -d cer -Uemt -p10864 cerdump

The 'funny' thing is that it works perfectly on some HP-UX systems and hangs
on some others. I've seen it happen on both IA and PA architectures. Also,
sometimes deleting some strings and restoring works, but the process is not

I attached gdb to the pg_restore process and here is the output of "bt":

(gdb) attach 9249
Attaching to program: /opt/iexpress/postgresql/bin/pg_restore, process 9249
0x60000000c058d890:0 in _poll_sys+0x30 () from /usr/lib/hpux32/
(gdb) bt
#0  0x60000000c058d890:0 in _poll_sys+0x30 () from /usr/lib/hpux32/
#1  0x60000000c05a2860:0 in poll+0x120 () from /usr/lib/hpux32/
#2  0x60000000c189ee90:0 in pqSocketPoll+0x120 ()
   from /usr/lib/hpux32/
#3  0x60000000c189ec10:0 in pqSocketCheck+0xb0 ()
   from /usr/lib/hpux32/
#4  0x60000000c189ea60:0 in pqWaitTimed+0x40 () from
#5  0x60000000c189ea00:0 in pqWait+0x40 () from /usr/lib/hpux32/
#6  0x60000000c189e6f0:0 in pqSendSome+0x150 () from
#7  0x60000000c18ab5a0:0 in pqEndcopy3+0x60 () from
#8  0x60000000c189a620:0 in PQendcopy+0x70 () from
#9  0x4019ef0:0 in _sendCopyLine+0x230 ()
#10 0x401a620:0 in ExecuteSqlCommandBuf+0x80 ()
#11 0x4013740:0 in ahwrite+0x2f0 ()
#12 0x401cdf0:0 in _PrintData+0x260 ()
#13 0x401c940:0 in _PrintTocData+0x2a0 ()
#14 0x4010540:0 in RestoreArchive+0xb30 ()
#15 0x400e960:0 in main+0xa80 ()

Another thing that happens is that postmaster always (well, almost always)
starts up saying 
FATAL:  the database system is starting up

I looked in the source code and saw that the canAcceptConnections function
in postmaster.c is returning CAC_STARTUP. Now, I don't have any applications
trying to connect when postmaster starts, so I am lost trying to figure out
why this is happening.

We are using PostgreSQL 7.4.2 throughout.

Any help will be greatly appreciated!  



pgsql-admin by date

Next:From: Chris White (cjwhite)Date: 2005-07-14 20:48:38
Subject: Error message: cannot identify operator 184
Previous:From: Thomas PundtDate: 2005-07-14 14:59:54
Subject: Re: Import Oracle to Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group