| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | keanld1(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16664: Problem running django |
| Date: | 2020-10-09 17:05:48 |
| Message-ID: | CA+bJJbyEJVZ1ee2kXoG7bgayUsrj-QnEo-DGRkhc44-hZy+hLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 9, 2020 at 6:55 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
.. very long and seemingly already truncated django/python exception
trace snipped...
> conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
> django.db.utils.OperationalError: fe_sendauth: no password supplied
> Please advise how to resolve?
Supply a password?
This does not seem like a Pg bug, but a django misconfiguration. Maybe
some django expert is lurking here and can solve it, but it seems like
you have somehow configured django without supplying a password for
the database.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-09 20:22:20 | Re: BUG #15858: could not stat file - over 4GB |
| Previous Message | David G. Johnston | 2020-10-09 17:04:52 | Re: BUG #16664: Problem running django |