From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PAM implementation in PG 9.2.3 |
Date: | 2013-05-13 11:57:47 |
Message-ID: | CA+h6Ahji7iKfnqamzq2vzQnDSHD6q1iVz5HV93xSSfLpu2P=cA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, May 13, 2013 at 11:17 AM, Amit Langote <amitlangote09(at)gmail(dot)com>wrote:
> > However, PG documentation doesn't highlight about this in psql or PAM
> > section, because log entries written are slightly confusing.
> > http://www.postgresql.org/docs/9.2/static/auth-methods.html
> > http://www.postgresql.org/docs/9.2/static/app-psql.html
>
> It turns out this logging is a bug in PAM authentication code in the
> backend that needs to resolved. This has been reported on
> pgsql-hackers.
>
>
>
Thank you.
--Raghav
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Singer | 2013-05-13 13:36:51 | Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4 |
Previous Message | Tim Kane | 2013-05-13 10:50:51 | Feature request: pg_restore with tablespace rules |