| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Mark Llewellyn <mark_llewellyn(at)adp(dot)com>, pgsql-hackers(at)postgresql(dot)org, Sujeet Rajguru <sujeet(dot)rajguru(at)enterprisedb(dot)com> |
| Subject: | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
| Date: | 2010-09-24 14:04:55 |
| Message-ID: | 13967.1285337095@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> I took a quick look at the code, and from what I can tell this is
> because PQconnectionNeedsPassword() always returns false if a
> pgpass.conf has been used. There is no handling the case where pgpass
> is used, but has an incorrect password.
Why should it? That code is complicated enough, I don't think it needs
to have a behavior of pretending that a wrong entry isn't there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-09-24 14:15:08 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
| Previous Message | Magnus Hagander | 2010-09-24 13:23:32 | Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-09-24 14:06:55 | Re: Standby registration |
| Previous Message | Dimitri Fontaine | 2010-09-24 14:01:06 | Re: Configuring synchronous replication |