Re: pg_restore hangs on 'some' HP-UX machines

Hi Chris,

<snip>
> So basically it is hanging when writing to the socket. Does
> this change if you use TCP/IP (say adding a -h localhost to
> your commandline)?
</snip>

This seems to work on one of my test machines where pg_restore was failing
before...still need to make sure that this will work always, but is
definitely a promising start.

Thanks a bunch!
Gopal.

> -----Original Message-----
> From: Chris Travers [mailto:chris(at)travelamericas(dot)com]
> Sent: Saturday, July 16, 2005 3:35 AM
> To: Gopal Srinivasa; pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] pg_restore hangs on 'some' HP-UX machines
>
> I don't have any experience on HP-UX so take this with a
> grain of salt...
>
>
>
> Gopal Srinivasa wrote:
>
> >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 repeatable.
> >
> >
> >
> I am assuming you are using ECC RAM, and that the hardware is
> good. If there is any doubt here, you may want to look into
> diagnostics on these areas.
>
> Just checking obvious things: Same version of libc on both
> working and nonworking systems? Any updates that you know of
> on working computers
> that are not on nonworking systems? What about the kernel
> (for socket
> handling)? Any difference there?
>
> >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/libc.so.1
> >(gdb) bt
> >#0 0x60000000c058d890:0 in _poll_sys+0x30 () from
> >/usr/lib/hpux32/libc.so.1
> >#1 0x60000000c05a2860:0 in poll+0x120 () from
> >/usr/lib/hpux32/libc.so.1
> >#2 0x60000000c189ee90:0 in pqSocketPoll+0x120 ()
> > from /usr/lib/hpux32/libpq.so.3
> >
> >
> <snip>
> So basically it is hanging when writing to the socket. Does
> this change if you use TCP/IP (say adding a -h localhost to
> your commandline)?
>
> In combination with the error about incomming connections, I
> wonder if something is up with the socket handling on the
> affected systems...
>
> Best Wishes,
> Chris Travers
> Metatron Technology Consulting
>
>