Re: BUG #5121: Segmentation Fault when using pam w/ krb5

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Ryan Douglas" <rdouglas(at)arbinet(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Date: 2009-10-15 21:19:38
Message-ID: 13870.1255641578@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Ryan Douglas" <rdouglas(at)arbinet(dot)com> writes:
> Whenever I use psql to remotely connect to the database the server crashes
> (see log below). If I use psql with the '-W' option then it's fine.

What this looks like at first glance is a bug in the PAM module you're
using, since Postgres really has no idea which PAM configuration is
being invoked. Can you get a stack trace to narrow down where the sig11
is happening? (You will probably need to insert "ulimit -c unlimited"
into the .bash_profile for Postgres to get the postmaster into a context
where it will produce a core dump.)

Also, is this your own build of Postgres, or if not whose?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2009-10-15 21:22:32 Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Previous Message Steve McLellan 2009-10-15 21:07:09 Re: BUG #5120: Performance difference between running a query with named cursor and straight SELECT