Postgres Pro
Downloads
Home   >   mailing lists

Thread: 7.2.3 / SuSe Linux / S/390

7.2.3 / SuSe Linux / S/390

From
Mike Blackwell
Date:
Anyone have this combination running?

7.2.3 built and runs fine on my RedHat 7.2 box.  Only partially works on
the S/390 Linux, with nearly identical config (no tcl on the 390).
Problem seems to be client processes segfaulting.  Some work:  PgAccess
from another machine seems fine; pg_dump seems ok.  Others die with
segfault: psql, as well as createuser and createdb, which use psql.

Any ideas whats going on?

FWIW, this is an upgrade from 7.1.2.

TiA,

Mike

Re: 7.2.3 / SuSe Linux / S/390

From
Neil Conway
Date:
Mike Blackwell <mblackwell@wallace.com> writes:
> Anyone have this combination running?
>
> 7.2.3 built and runs fine on my RedHat 7.2 box.  Only partially works on
> the S/390 Linux, with nearly identical config (no tcl on the 390).
> Problem seems to be client processes segfaulting.  Some work:  PgAccess
> from another machine seems fine; pg_dump seems ok.  Others die with
> segfault: psql, as well as createuser and createdb, which use psql.

Can you get a backtrace from one of the core dumps using gdb? As is,
there's not a whole lot of information to go on...

Cheers,

Neil

--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC

Re: 7.2.3 / SuSe Linux / S/390

From
Tom Lane
Date:
Mike Blackwell <mblackwell@wallace.com> writes:
> 7.2.3 built and runs fine on my RedHat 7.2 box.  Only partially works on
> the S/390 Linux, with nearly identical config (no tcl on the 390).
> Problem seems to be client processes segfaulting.  Some work:  PgAccess
> from another machine seems fine; pg_dump seems ok.  Others die with
> segfault: psql, as well as createuser and createdb, which use psql.

Shared library mismatch perhaps?  See if you can get a stack trace from
the psql segfault.

            regards, tom lane